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.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Why AI Agents and MCP Servers Just Became a CISO’s Most Urgent Priority”.
Key questions
Q: What breaks when AI agents can reach exposed internal APIs?
A: The break point is governance, not just security tooling.
Q: Why do MCP servers create more risk than traditional APIs?
A: MCP servers create more risk because they centralize access, make tools discoverable at runtime, and often sit close to the secrets that authenticate downstream calls.
Q: What are the signs that API governance is failing at runtime?
A: Common signs include undocumented endpoints, duplicated ownership, inconsistent responses, rising retry loops, and frequent discovery of APIs that are not in the catalogue.
Practitioner guidance
- Inventory every API used by agents and MCP servers Build a live map of internal, partner, and dynamically created APIs that autonomous systems can reach, then reconcile it against approved business use cases.
- Apply task-scoped authorisation to agent tool use Constrain each agent and MCP server to the narrowest set of APIs, methods, and data objects required for a specific workflow.
- Move monitoring to the API execution path Instrument runtime visibility for requests between agents, MCP servers, and downstream services so policy violations are observable inside the environment.
Bottom line: Agentic AI shifts the main security question from model behaviour to API-layer control over actions, data access, and workflow execution.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:25 pm
API fabric governance is now the real boundary for agentic systems. Once software can choose actions and call tools, the security question shifts from whether the model is safe to whether every downstream API call is authorised, visible, and revocable. Perimeter tooling was built for known ingress and egress patterns, not for dynamic machine-driven orchestration across internal services. Practitioners should treat API governance as the operational centre of agentic AI security.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- Half of companies using generative AI will deploy agentic AI by 2027, according to Deloitte's 2025 Technology Predictions.
A question worth separating out:
Q: How should teams respond when an MCP server or agent behaves outside declared purpose?
A: Suspend the agent's connection path first, then revoke or narrow the credentials that allowed the unexpected access. The goal is to stop the action before it completes and preserve the audit trail for investigation. After containment, reclassify the server or agent as a high-risk integration until the control gap is understood.
👉 Read our full editorial: Agentic AI and MCP servers are expanding the API attack surface