Notifications
Clear all
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.
NHIMG editorial — based on content published by Akto: Best MCP Discovery Tools in 2026
Questions worth separating out
Q: How should security teams govern MCP access in agentic workflows?
A: Security teams should govern MCP access as delegated identity, not simple application connectivity.
Q: Why do MCP deployments increase identity and access risk?
A: MCP increases risk because it connects untrusted model output to real systems that can act on it.
Q: What breaks when MCP tools are exposed without policy controls?
A: Without policy controls, MCP tools become a discoverable privilege surface rather than a governed capability set.
Practitioner guidance
- Map every MCP endpoint to an owning identity Build an inventory that ties each MCP server, connector, and API path to an accountable owner, an approved use case, and an expiry review date.
- Review agent-to-tool permissions as one control set Combine agent access review, tool authorization, and permission analysis into a single workflow so teams can see when an agent has broader tool reach than the task requires.
- Enable continuous change tracking for MCP-connected services Alert on new servers, connector changes, permission shifts, and unusual tool invocation patterns.
What's in the full article
Akto's full blog covers the operational detail this post intentionally leaves for the source:
- Specific feature descriptions for automated MCP server and API detection across cloud, hybrid, and on-prem environments
- The vendor's comparison of static, dynamic, agent-centric, and network-based discovery approaches
- Tool-by-tool positioning across Akto, Kong, Lasso Security, Prompt observability platforms, and MCP-Manager
- Detailed claims about prompt injection, tool poisoning, insecure auth, and data leak testing inside discovered MCP endpoints
👉 Read Akto's guide to the best MCP discovery tools in 2026 →
MCP discovery tools: what IAM and security teams need to see?
Explore further
02/08/2026 1:17 pm
MCP discovery is becoming an identity control, not just an inventory function. Once AI agents can reach tools through MCP, the security question shifts from "what exists" to "what can act on what." That is an identity governance problem because discovery must expose permissions, tool paths, and approval boundaries, not just endpoints. Practitioners should treat MCP visibility as part of NHI governance.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface report.
A question worth separating out:
Q: What should teams do when an MCP server appears outside the approved inventory?
A: Treat the server as an unmanaged trust relationship until proven otherwise. Pause agent access, validate ownership, confirm the intended integration, and check whether the connector exposes data or command paths that were never reviewed. In agentic systems, an unknown tool is already part of the attack surface.
👉 Read our full editorial: MCP discovery tools are becoming identity control points for AI agents
