Topic starter
09/07/2026 3:25 pm
TL;DR: Just-in-time access works for humans because requests are rare, reviewable, and accountable, but AI agents generate constant, machine-speed access requests that can be manipulated through prompt injection, according to Clutch Security. The real failure is assuming a sentence can safely stand in for governed identity and lineage.
Editorial analysis by NHI Mgmt Group, based on content published by Clutch Security: “Intent? What Intent? Why JIT Falls Apart for AI Agents”.
Key questions
Q: What breaks when just-in-time access is used for AI agents?
A: It breaks because JIT assumes a human request that is deliberate, reviewable, and accountable.
Q: Why do AI agents make excessive access more dangerous than human access?
A: AI agents can use inherited permissions continuously, across multiple systems, and at machine speed.
Q: How do security teams know if an AI agent has too much access?
A: Look for agents that can reach multiple systems without task-specific limits, use persistent tokens, or touch high-value services such as email, chat, cloud consoles, and file stores.
Practitioner guidance
- Map every agent to a real identity Inventory the non-human identities an agent can assume, the human owner behind each one, and the systems each identity can reach before any access is granted.
- Remove intent as a trust signal Treat prompt text, tickets, README files, and other agent inputs as untrusted content when they influence authorisation decisions or access brokerage.
- Replace request-based JIT with platform-bound ephemerality Use workload-bound, short-lived credentials that are issued through verified identity controls rather than through a model-generated access request.
Bottom line: Just-in-time access fails for AI agents because the control depends on human-style intent, review, and accountability that agent workflows do not provide.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 3:44 pm
Intent-based JIT is a control designed for human requests, not autonomous access generation. Human requests are rare, deliberate, reviewable, and attributable. AI agent requests are continuous, machine-generated, and mutable inside the same task. That means the governance assumption behind JIT collapses before the credential is even issued. The implication is that authorisation design must stop treating declared intent as the primary trust signal.
A few things that frame the scale:
- 59% of organisations say they lack viable alternatives to standing privileged access for NHIs and AI agents, according to Delinea research.
A question worth separating out:
Q: Should organisations use workload identity instead of request-based JIT for AI agents?
A: In most cases, yes, because verified workload identity binds short-lived credentials to a known machine or service context. That is different from minting access because a model produced a plausible sentence. The decision point is whether the organisation wants ephemerality enforced by platform trust or merely promised by generated text.
👉 Read our full editorial: Why just-in-time access fails for AI agent identities