Topic starter
02/08/2026 12:15 pm
TL;DR: As MCP adoption grows, discovery tools are being used to detect servers, map agent-tool relationships, and monitor AI-to-API interactions across cloud, hybrid, and on-prem environments, according to Akto. The governance issue is not visibility alone but whether identity, permissions, and oversight can keep pace with fast-changing agentic connections.
Editorial analysis by NHI Mgmt Group, based on content published by Akto: “Best MCP Discovery Tools in 2026”.
Key questions
Q: What breaks when MCP access is not centrally enforced?
A: When MCP access is not centrally enforced, agents can bypass the sanctioned protocol and reach the same data through alternative connectors or direct application paths.
Q: Why do MCP environments increase identity governance complexity for AI agents?
A: MCP turns model-tool interaction into a repeatable identity event, which means access, logging, and approvals must work at the capability level rather than at the application level.
Q: How do security teams know whether an MCP gateway is actually working?
A: Look for three signals: tool-level policy enforcement, before-execution blocking or approval, and a complete audit trail tied to a real owner.
Practitioner guidance
- Build a live MCP asset map Catalogue every MCP server, tool, and external API connector across cloud, hybrid, and on-prem environments, then keep the map updated as new services appear.
- Tie discovery to permission review Inspect each discovered MCP connection for excessive or unused privileges, then remove access that is not justified by the agent’s current workflow.
- Track shadow MCP endpoints continuously Run ongoing scans and alerting for undocumented servers, new connectors, and changed access paths so shadow MCP does not persist between review cycles.
Bottom line: MCP discovery is only useful when it becomes part of identity governance and not just asset inventory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:17 pm
MCP discovery is becoming an identity control point, not just an inventory function: once agents can select tools and invoke APIs across environments, the governance question shifts from whether a server exists to whether its access path is understood and controlled. That makes discovery part of IAM evidence, not a separate observability layer. Practitioners should treat the resulting inventory as a live entitlement map, not a static asset list.
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.
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should IAM teams do after finding shadow MCP assets?
A: They should treat the finding as an access governance issue, not a documentation cleanup task. The next step is to confirm ownership, validate whether the asset should exist, and revoke or scope back any privileges that are not required. Shadow MCP matters because unknown endpoints often hide unknown access paths.
👉 Read our full editorial: MCP discovery tools are becoming identity control points for AI agents