Topic starter
02/08/2026 11:46 am
TL;DR: AI agents call APIs, trigger workflows, and modify systems after the model layer, leaving most security tooling blind to the actions that create real risk, according to Salt. The action layer, not prompt security alone, is where agentic governance becomes operationally necessary.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Everyone Is Securing the Wrong Layer of AI”.
Key questions
Q: What breaks when AI agent behaviour is only monitored at the prompt layer?
A: Prompt-layer monitoring misses the point where risk becomes real, which is tool use, data movement, and chained actions inside the session.
Q: Why do AI agents increase IAM and PAM risk?
A: AI agents increase IAM and PAM risk because they can execute actions quickly once privilege is available, which shortens the time available to detect misuse.
Q: What are the signs that agentic security testing is failing?
A: Common failure signs include inflated finding volumes, repeated false positives, opaque reasoning, results that cannot be reproduced, and test actions that drift beyond approved scope.
Practitioner guidance
- Inventory all agent action paths Identify every API, workflow engine, database, and third-party service an agent can reach, including MCP-connected and shadow deployments.
- Baseline normal agent behaviour Define what normal looks like for each agent by frequency, endpoint, payload shape, and task context.
- Apply runtime authorization to tool use Require explicit authorization checks for agent actions that write data, move money, modify systems, or chain across services.
Bottom line: The central risk in agentic AI is not prompt misuse alone but the ability of an authorised agent to take harmful actions through APIs, workflows, and downstream systems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:57 pm
Action layer security is now the missing control plane for agentic governance. The article is right to separate model safety from execution safety, because the real risk emerges when a delegated system can act across APIs and workflows. That shifts the governance question from what the model said to what the agent was allowed to do in the environment. Practitioners should treat action visibility as a core identity and access control requirement, not a monitoring nice-to-have.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: How should teams decide between API governance and MCP governance for agents?
A: Use API governance for the backend service boundary and MCP governance for the agent-facing tool boundary. The two overlap, but they solve different problems: one secures the service surface, the other constrains how agents discover and consume that surface.
👉 Read our full editorial: Action layer security is the missing control for AI agents