Topic starter
02/01/2026 10:37 am
TL;DR: MCP adoption is surfacing a governance gap where agents face context overload, inefficient tool selection, and weak enterprise knowledge handling, according to Astrix Security, while Anthropic’s example shows 5 MCP servers can expose 58 tools and about 55,000 tokens before a conversation starts. Tool discovery and agent skills reduce context bloat, but they also make access scoping, provenance, and operational review harder to defer.
Editorial analysis by NHI Mgmt Group, based on content published by Astrix Security: “MCP’s First Year: The Missing Security Pieces Are Finally Falling Into Place (Part 2)”.
Key questions
Q: What breaks when agents are given too many MCP tools at once?
A: Agents can lose the ability to choose the right tool cleanly, especially when tool definitions, parameters, and response formats all enter the prompt at once.
Q: Why does deferred tool discovery change the governance model for agents?
A: Because the agent’s effective capability set is no longer fixed at session start.
Q: How should organisations govern agent skills in enterprise environments?
A: Treat skills as reusable knowledge packages that need classification, scope limits, and review just like other non-human identity assets.
Practitioner guidance
- Inventory agent-facing tools Map every MCP server and exposed tool that can enter an agent workflow, then flag which ones are always loaded and which can be deferred or hidden.
- Set discovery boundaries Define which tools may be discoverable by default, which require explicit task context, and which should never be surfaced to general-purpose agents.
- Separate skills by sensitivity Create a review process for skill directories so that operational scripts, brand guidance, and other enterprise context are grouped by sensitivity and task scope.
Bottom line: MCP tool discovery is shifting governance attention from static access lists to runtime capability selection and context loading.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 4:27 pm
Tool discovery is becoming an identity governance control surface: The article shows that MCP governance is no longer only about who can connect to what, but about what an agent can discover, rank, and select at runtime. That means tool exposure now affects operational identity behaviour, not just interface design. The practical consequence is that discovery logic must be treated as part of the access model.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How do tool discovery and skills affect access review for AI agents?
A: They make review harder if the organisation only tracks static entitlements. An agent may discover tools or load skills only when a task requires them, so the reviewable state shifts from provisioned access to runtime exposure. Security teams should therefore validate both the baseline entitlement and the discovery path that makes additional capability available.
👉 Read our full editorial: Agent tool discovery and skills are reshaping MCP governance