Giving every agent every MCP tool backfired, so they built virtual servers
Background-Job-862 · reddit · 2026-07-26
A team says exposing every tool from every MCP server to every agent turned out to be a mistake.
They had about 15 MCP servers registered, and each connected agent could see the full tool list. That caused two problems:
- Tool selection got worse as the list grew to 80+ tools; the model started choosing vaguely similar tools from the wrong server.
- Security scoping was too broad because agents could see tools they had no business touching.
Their fix was to introduce a virtual MCP server:
- Curate a small, scoped subset of tools from multiple real servers.
- Present that subset as one server per team, workflow, or agent.
- Example: a customer-support bot sees only ticketing and CRM tools, not billing or infra tools.
Unexpected upside: tool selection improved, and security reviews became much easier because the virtual server’s tool list clearly defines what the agent can do.
More from coding & agent
- NVIDIA says Nemotron 3 Ultra hit 97.1% on agentic RTL chip-design tasks — NVIDIAAI · 2026-07-27
- Tokyo Agent Forge hackathon shipped production-ready AI agents in one day — DavidBennett__ · 2026-07-27
- Long-running agents will need immutable event logs, this thread argues — sebpaquet · 2026-07-27
- Agentic Data Science in Practice: Agents Write Code but Answer Wrong Questions — hugobowne · 2026-07-27
- A VS Code extension adds Markdown-style highlighting to Alchemy string templates — samgoodwin89 · 2026-07-27
- Claude’s Stripe MCP connector is being called unusable after repeated disconnects — evielync · 2026-07-27