Topic starter
02/08/2026 11:36 am
TL;DR: A lack of visibility into agents, MCP servers, and API connections leaves most organisations unable to govern agentic environments, and CSA research cited by Salt says 82% have found unknown AI agents while 65% have already seen an AI-agent-related incident. The control problem is now context, not just inventory: who can do what, through which path, and at what blast radius.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Your AI Agents Are Already Acting. The Question Is Whether You Can See What They’re Doing.”.
Key questions
Q: What breaks when agentic AI is deployed without formal security policies?
A: Without formal policies, agentic AI can accumulate access, generate defects, and trigger unsafe actions faster than security teams can govern them.
Q: Why do machine identities and MCP servers increase risk in agentic environments?
A: Because they create delegated access paths that can outlive the original approval decision and reach sensitive systems at machine speed.
Q: What are the signs that agentic access is escaping formal governance?
A: The clearest signals are unmanaged agents, inconsistent onboarding, permissions granted outside IAM policy, and gaps between what an agent can reach and what the access model says it should reach.
Practitioner guidance
- Map agents, MCP servers, and APIs as one control plane Build an inventory that connects each agent to the MCP servers it uses and the APIs those servers can reach.
- Constrain MCP permissions to the minimum reachable scope Review every MCP server for the specific tools, data sources, and actions it can expose to an agent.
- Baseline agent behaviour by path and payload Use behavioural monitoring to identify when an agent starts calling unfamiliar APIs, expanding query volume, or changing action sequences.
Bottom line: Most organisations have begun deploying agents faster than they can map the relationships those agents create across MCP servers and APIs.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:50 pm
Agentic governance has a visibility problem before it has a policy problem: organisations cannot control what they cannot map. The article correctly shifts attention away from whether agents exist and toward whether their relationships are known, approved, and bounded. For IAM and security teams, the practical conclusion is that discovery and relationship context now sit ahead of enforcement maturity.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, 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 security teams respond when agentic access paths are too broad?
A: They should narrow access to the minimum reachable scope, then tie review and offboarding to the actual agent-to-MCP-to-API path rather than to the agent alone. The goal is to make blast radius visible and then make it smaller, so governance decisions reflect what the system can truly do.
👉 Read our full editorial: Agentic security graph visibility is becoming the AI control gap