Topic starter
02/08/2026 12:17 pm
TL;DR: Agentic AI security is maturing into a five-layer stack, with Akto framing the shift around discovery, identity, runtime guardrails, MCP visibility, and continuous red teaming. The stack only works if agent behavior, tool access, and downstream actions are governed together.
Editorial analysis by NHI Mgmt Group, based on content published by Akto: “Agentic AI Security: The Current Market Landscape”.
Key questions
Q: Why do agent credentials create more risk than traditional IAM models expect?
A: Traditional IAM models assume the identity behind an action is stable enough to inspect, review, or challenge.
Q: What breaks when MCP servers are connected without a trusted control plane?
A: Discovery and execution become the same decision, which removes the ability to review who published a tool, who can call it, and what trail exists after use.
A: They should build a single inventory of agents, MCP servers, tools, and data flows before deciding which team owns which control.
Practitioner guidance
- Map the agentic action surface Inventory agents, MCP servers, tools, data flows, and downstream APIs before assigning control ownership.
- Separate identity from runtime enforcement Treat credentials, tokens, and permissions as the identity layer, then decide where behavioral checks and blocking should occur during execution.
- Establish MCP boundary controls Place policy enforcement where tools and resources are exposed so shadow servers and unknown integrations do not bypass governance.
Bottom line: Agentic AI security is maturing into a layered control problem that spans discovery, identity, runtime enforcement, MCP visibility, and adversarial testing.
Glossary terms: Agentic AI Security, MCP Boundary, Agent Identity, Agent Surface
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
02/08/2026 1:19 pm
Agentic AI security is becoming an action-surface governance problem, not a prompt-safety problem. The article correctly shows that the security boundary now includes agents, tools, MCP servers, and downstream systems. That shift matters because governance models built around static applications do not describe how a runtime decision engine acquires and uses capability. Practitioners should treat control design as a question of who can initiate action, not only who can see output.
A few things that frame the scale:
- Gartner predicts that by the end of 2026, 40% of enterprise apps will feature task-specific AI agents.
A question worth separating out:
Q: How can organisations prove their AI controls are actually working?
A: Look for evidence that policy decisions are logged, sensitive prompts are being redacted or blocked when required, and approved AI interactions are traceable by identity and business context. Effective programmes produce audit-ready records, not just policy text. If the control cannot explain what happened in a session, it is not operational enough.
👉 Read our full editorial: Agentic AI security stacks are converging around five layers