Notifications
Clear all
Topic starter
02/08/2026 11:24 am
TL;DR: Enterprises are deploying AI agents that call APIs, read databases, move files, and trigger production actions through MCP servers, yet many organisations still lack a clear inventory of what those agents can access, according to Akto. Least-privilege enforcement, audit trails, and continuous review now define whether agentic AI stays governable or becomes an unmanaged attack surface.
NHIMG editorial — based on content published by Akto: Agentic AI Security How to Audit MCP Server Permissions for Enterprise AI Agents
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%).
Questions worth separating out
Q: How should security teams design MCP server access for AI agents?
A: Security teams should design MCP access around a small set of agent goals, not a mirrored list of REST endpoints.
Q: Why do broad MCP permissions increase AI agent risk?
A: Broad permissions expand the blast radius of any prompt injection, configuration error, or credential compromise.
Q: What signals show an MCP environment is out of control?
A: Common warning signs include unknown MCP servers, shared credentials across agents, broad tool access, unused permissions that were never revoked, missing approval workflows, and weak audit trails.
Practitioner guidance
- Inventory every MCP server and connected agent Build a complete list of MCP servers, the agents attached to them, and the tools, APIs, databases, and file systems each one can reach.
- Review authorization grants against actual task use Compare granted permissions with observed usage and remove access that is broad, dormant, or no longer business justified.
- Separate high-risk tools from routine agent workflows Create tighter controls around deployment, deletion, payment, and production-data tools than around low-risk read-only operations.
What's in the full article
Akto's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step MCP server inventory method for cloud accounts, endpoints, and on-premises assets
- Permission matrix examples that show how to spot overprovisioned agent-to-tool grants
- Continuous testing and runtime guardrail workflow for validating agent authorization
- Governance checklist for ownership, review cycles, reporting, and monitoring
👉 Read Akto's guide to auditing MCP server permissions for enterprise AI agents →
MCP server permissions audit: is your agent access actually scoped?
Explore further
02/08/2026 12:41 pm
Permission sprawl is now the defining governance problem for agentic AI. MCP makes tool connectivity simple, but that convenience also hides how many systems an agent can reach. When access is granted faster than it is reviewed, the identity problem shifts from authentication to authority management. Practitioners need to treat every new MCP grant as a change to the enterprise attack surface, not a routine integration detail.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), 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.
A question worth separating out:
Q: What should organisations do when AI agent security is changing faster than review cycles?
A: They should shift from periodic approval to continuous governance. That means automated pre-deployment red teaming, runtime guardrails, change-triggered retesting, and access recertification for tools and data sources. The goal is to govern the agent as a live identity with evolving scope, not as a one-time software release.
👉 Read our full editorial: Auditing MCP server permissions is now core to AI agent security
