Topic starter
02/08/2026 11:28 am
TL;DR: AI agents create risk when they take the wrong action, not just when they answer badly, because prompts can flow through runtimes, MCP servers, tools, and downstream APIs before security teams see the impact, according to Salt. The governance gap is visibility into who or what authorised the action, because agentic systems collapse traditional prompt-level controls into runtime decisions that IAM cannot review after the fact.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Deconstructing the Agentic Stack: Why API Visibility Is the Ultimate Defense for AI Agents”.
Key questions
Q: What breaks when an AI agent is allowed to call tools without strict scope controls?
A: The main failure is privilege expansion.
Q: Why do AI agent actions create more governance risk than prompt errors alone?
A: Prompt errors matter, but the operational damage usually happens when an agent is permitted to act.
Q: What are the signs that agentic pipeline controls are failing?
A: Look for agents reaching for secrets outside declared scope, unexpected outbound calls, pushes to protected branches, and shell commands that cross policy boundaries.
Practitioner guidance
- Map agent-to-tool-to-API execution paths Inventory every agent runtime, MCP server, custom tool, and downstream API that can be reached from an AI workflow.
- Bind API actions to the originating agent identity Require telemetry that links API calls back to the agent, prompt, tool, and user session that triggered them.
- Scope tool permissions to task-specific authority Limit custom tools and MCP-accessible functions to the smallest set of actions needed for the workflow.
Bottom line: AI agents change security from an output-quality problem into an action-authorisation problem once tools and APIs are in scope.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:43 pm
Prompt-level security is no longer the control boundary: The article shows that the real security event happens when an agent converts a request into an action. That means the industry has moved from evaluating text outputs to governing runtime authority, tool selection, and downstream API reach. For identity teams, the important question is no longer only what the model said, but what the system was allowed to do next.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should teams govern AI agents that can reach APIs, events, and memory?
A: Teams should govern those agents as runtime identities, not as isolated integrations. That means enforcing policy at execution time, logging every tool and data access, and binding actions back to a clear initiating workflow or identity. If the control plane cannot show who acted, what they reached, and why, the programme does not have usable governance.
👉 Read our full editorial: AI agent risk is moving from prompts to API actions