TL;DR: Agentic AI is shifting control from login events to runtime decisions that can trigger real actions, with VotalAI in the middle of that shift. Runtime policy enforcement and delegated identity have to sit inside the execution path, or access review arrives after the decision that mattered.
Editorial analysis by NHI Mgmt Group, based on content published by VotalAI: “The Runtime Between Two Ages of AI”.
Key questions
Q: Why do static credentials create problems for agentic AI access control?
A: Static credentials assume authority changes slowly enough for human review and periodic rotation.
Q: What breaks when agent permissions are reviewed after deployment instead of at runtime?
A: Post-deployment review assumes privileges remain stable long enough to be observed and certified.
Q: How should teams govern agentic access when AI systems move faster than access reviews?
A: Teams should move governance earlier in the lifecycle and treat issuance, delegation and device trust as the main control points.
Practitioner guidance
- Define agent identity as a governed class Model agents separately from human users and service accounts, with explicit delegation, scope, and expiry rules for each runtime token.
- Move authorisation into the execution path Require policy evaluation before tool invocation and again after action completion so that unsafe calls never rely on log review alone.
- Inventory every tool exposed to agents Map each MCP or gateway endpoint to an owner, an allowed purpose, and a maximum privilege boundary before the endpoint is reachable.
Bottom line: Agentic AI changes the identity problem by moving control from login events to runtime decisions that can trigger real actions.
Glossary terms: Agent Identity, Runtime Authorisation, Delegated Access, MCP Gateway
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Runtime guardrails are becoming the real control plane for agentic AI. The article is strongest when it treats policy enforcement as something that must occur during execution, not after the fact. That is a shift from classic IAM thinking, where authentication and authorisation are front-loaded and monitoring is reactive. For agentic systems, the decisive control is whether the runtime can inspect, authorise, and record the action before the tool call completes.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between human identity and agent identity in IAM design?
A: Human identity is built around a person who authenticates and then acts. Agent identity must also represent delegated purpose, tool authority, and session lifespan, because the actor can select actions at runtime. That means the same access model cannot be copied unchanged from users to autonomous systems.
👉 Read our full editorial: Runtime guardrails define the next control plane for agentic AI