Notifications
Clear all
Topic starter
06/09/2026 6:21 pm
TL;DR: AI agents can send messages, delete files, and write to databases in seconds through MCP-connected tools, with no approval workflow or audit trail until after the fact, according to SailPoint. The real governance problem is runtime enforcement, because agentic access assumptions break when actions can chain across tools faster than human review cycles can intervene.
NHIMG editorial — based on content published by SailPoint: AI agents are acting without your permission. Here's how to govern them
Questions worth separating out
Q: What breaks when AI agents bypass a centralized MCP gateway?
A: When agents bypass a centralized MCP gateway, security controls fragment across notebooks, scripts, and individual servers.
Q: Why do AI agents make non-human identity governance harder?
A: AI agents make governance harder because they can request tools, act autonomously, and change behaviour across sessions while still relying on machine credentials.
Q: What are the signs that agentic access controls are failing?
A: The main signs are invisible tool use, delayed discovery of actions, and audit logs that explain an outcome only after it has already occurred.
Practitioner guidance
- Define policy at the action layer Create allow and deny rules for read, write, delete, and send operations against specific MCP-connected targets, so controls evaluate the request before execution.
- Inventory agent-to-tool pathways Map every AI agent, every MCP server, and every reachable resource so you can see where agent actions can cross system boundaries without review.
- Separate visibility from enforcement Keep session logging and audit trails, but do not treat them as control.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- The exact Discover-Govern-Protect to enforcement breakdown used to position agent governance inside an identity programme.
- Policy examples for specific agent, target, and action combinations across MCP-connected tools.
- What session logs show when an agent request is blocked at the policy line.
- How SailPoint describes Agentic Access Administration as the enforcement layer in its architecture.
👉 Read SailPoint's analysis of AI agent governance through MCP access controls →
AI agent actions through MCP servers: are your controls keeping up?
Explore further
06/09/2026 6:21 pm
Agentic access governance is not a permissioning problem, it is an execution problem. The article shows that AI agents can already act through enterprise tools without a human approval gate, which means the control failure happens at the moment of action rather than at authentication. IAM teams that treat agents as another login surface will miss the real risk boundary. The practical conclusion is that action-level policy must become a first-class identity control.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, while 60% more plan to do so within 12 months.
A question worth separating out:
Q: Should organisations treat autonomous agents like human users or service accounts?
A: Organisations should not treat autonomous agents as simple human analogues. They behave like governed non-human identities with added runtime decision-making, so they need identity boundaries, action checkpoints, and clear accountability. Human-style certification cycles alone are too slow for systems that can complete sensitive work within one session.
👉 Read our full editorial: AI agent access governance depends on enforcement at runtime
