Notifications
Clear all
Topic starter
02/08/2026 12:26 pm
TL;DR: Agentic AI and Model Context Protocol servers are turning APIs into the primary control plane for autonomous actions, while traditional edge tools often miss the traffic that matters, according to Salt. The security gap is no longer model-centric: governance, visibility, and containment must move to the API layer before agentic systems outpace existing controls.
NHIMG editorial — based on content published by Salt: Agentic AI and MCP servers are reshaping the attack surface
By the numbers:
- 96% of technology professionals identify AI agents as a growing security threat, and 66% believe this risk is immediate.
- 53% of MCP servers expose credentials through hard-coded values in configuration files.
Questions worth separating out
Q: How should security teams govern AI agents that call APIs instead of using a UI?
A: Security teams should govern AI agents by treating each callable action as a scoped entitlement, not as a general application login.
Q: Why do MCP servers create new risk for IAM teams?
A: MCP servers can collapse the boundary between human intent and machine execution.
Q: What breaks when AI agent traffic is only monitored at the edge?
A: Edge-only monitoring misses the internal API calls where most agentic action occurs.
Practitioner guidance
- Inventory every agent-facing API path Build a live inventory of the APIs, internal services, and third-party endpoints that AI agents and MCP servers can call.
- Move policy enforcement into the API layer Apply authorization and policy checks at the point of API execution so machine actions are evaluated in context.
- Instrument agent activity for audit and response Log which agent invoked which API, with what context, against which data source, and whether the request was approved, denied, or modified.
What's in the full article
Salt's full article covers the operational detail this post intentionally leaves for the source:
- The vendor's five CISO questions for mapping AI agent and MCP server API exposure.
- Real-time visibility considerations for API traffic between agents, MCP servers, and internal or third-party data sources.
- Guidance on applying governance and policy controls at the API layer for AI-driven actions.
- Containment priorities for stopping a rogue agent or compromised MCP server before data or systems are affected.
👉 Read Salt's analysis of agentic AI, MCP servers, and API security →
Agentic AI and MCP servers: what does this mean for API security?
Explore further
02/08/2026 1:25 pm
API visibility debt is now an identity governance problem. When AI agents and MCP servers issue actions through hidden or dynamic APIs, organisations lose the ability to prove who or what accessed data, which policy applied, and whether the action stayed inside scope. That creates governance debt because access review, audit, and incident response all depend on a reliable trail. Practitioners should treat API telemetry as part of identity control, not a separate monitoring concern.
A question worth separating out:
Q: Who is accountable when an AI agent exceeds its intended scope?
A: Accountability should follow the delegation chain, not stop at the agent label. The human requester, the policy owner, and the team that granted underlying access all matter, because the agent acts within a permission model someone designed. If the chain is unclear, the governance model is already too weak.
👉 Read our full editorial: Agentic AI and MCP servers are expanding the API attack surface
