We Shipped Per-Tool Toggle Controls for Our MCP Server — Here's Why It Matters More Than It Sounds

We Shipped Per-Tool Toggle Controls for Our MCP Server — Here's Why It Matters More Than It Sounds If you've been building AI agent integrations with Model Context Protocol, you've probably hit this wall: you connect an LLM to a data source via an MCP server, and suddenly the agent has access to everything that server exposes. Every tool. Every endpoint. Every table. That's fine in a sandbox. It's a security incident waiting to happen in production. DreamFactory 7.4.3 (shipping alongside df-mcp-server v1.2.0 and df-admin-interface v1.7.1) adds per-tool toggle controls directly in the MCP Server configuration page. It's a small UI change with a non-trivial impact on how you govern AI agent access to enterprise data. Let me walk through the problem we were solving and what the implementation actually looks like. The Real Problem With MCP in Enterprise Environments MCP is genuinely useful. It gives LLMs a standardized way to call tools — query a database, read a file, hit an API — without