Topic starter
27/06/2026 1:03 pm
TL;DR: PlainID shows that AI agents break the assumptions behind human and machine IAM because they decide at runtime, chain tools and operate at scale. Static, login-time authorization cannot evaluate intent across the prompt, data, tools and response, so policy must move to runtime decisioning.
Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “Intent-Based Access Control for AI Agents”.
Key questions
Q: What breaks when AI authorization happens only at login?
A: A login-only model assumes the session stays safe after authentication, but AI systems may make many later decisions and tool calls across multiple services.
Q: Why do AI agents need runtime intent evaluation?
A: Because the meaningful authorization question is not just who is logged in.
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
- Map agent decision points Identify where your AI agents can prompt, retrieve data, invoke tools and return responses, then classify each as a separate authorization surface.
- Bind user and agent identity Require policy decisions to evaluate the human requester, the agent identity, the requested action and the current context together.
- Enforce runtime checks Move sensitive approvals away from login-time checks and apply them at the moment each agent operation is about to commit.
Bottom line: AI agents do not fit cleanly into login-time authorization because they decide and act after the initial access check.
What's in the full article
PlainID's full article covers the operational detail this post intentionally leaves for the source:
- The four-point control model across prompt, data, tools and response in more implementation detail
- The runtime authorization pattern across code-first, low-code, production runtime and gateway surfaces
- The article's framing of intent-based access control as a policy language for agentic AI
- The practical discussion from EIC 2026 on how the model applies in regulated enterprises
👉 Read PlainID's analysis of intent-based access control for AI agent governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
27/06/2026 2:13 pm
Runtime intent, not session start, is the new control boundary for agentic AI. The article shows that login-time checks cannot keep pace with agents that chain tools and choose actions after the session opens. That makes intent evaluation a runtime identity problem, not a one-time access grant. The implication is that AI agent governance must be designed around continuous authorization decisions, not inherited from human IAM patterns.
A few things that frame the scale:
- 62% of organisations are at least experimenting with AI agents, but only 23% have scaled one into a single business function, according to McKinsey's 2025 State of AI survey.
A question worth separating out:
Q: How should teams govern AI agents that run across multiple runtimes?
A: Teams should govern them with a shared trace schema, consistent evaluation criteria, and clear ownership for tool access. Portability changes the execution layer, but it does not remove the need to prove what the agent did, why it did it, and whether the behaviour stayed inside policy across environments.
👉 Read our full editorial: Intent-based access control is redefining AI agent governance