MCP Dev Summit North America

Tool sprawl is a common failure mode for enterprise agents: the more tools an agent can reach, the less predictable it becomes—driving hallucinations, higher token costs, and larger security blast radius. Scaling agents safely requires specialization enforced by capability boundaries, not just better prompts.

This talk explores MCP best practices through a managed implementation where MCP servers are declared as explicit collections of tools and treated as governed objects. Specialization comes from two independent boundaries: (1) the MCP server definition limits the tool surface an agent can even access, and (2) RBAC still applies inside that server—so a user can only invoke tools they’re authorized to use, even if they can access the server that contains them.

Together, these boundaries reduce sprawl while improving operability: agents become easier to reason about, costs drop because fewer tools are in play, and least privilege is enforced with practical, role-aligned granularity.