Learn · Access
Contain blast radius: over-privileged service accounts and just-in-time agent access
Blast radius is how much damage one compromised or misled agent can do. Agents that run on a shared, over-privileged service account have a large one: everything the account can reach. You shrink it by giving each agent its own identity and authorizing each call against a narrow boundary.
Why service accounts grow too powerful
A service account is created once and shared. Over time it collects permissions for every task anyone needed, and nobody wants to remove one in case something breaks. When an agent runs on it, the agent inherits all of it.
How to shrink the radius
- Per-agent identity so one agent's access is not another's.
- An operational boundary listing the services, tools and arguments each agent may use.
- Audience-bound tokens that name one service and last at most 300 seconds, or 60 for privileged capabilities.
- A decision per call, so access is granted for the operation at hand and not held in advance.
Just-in-time authorization
Just-in-time access means authority exists only when needed. Here that is concrete: the agent holds a token of minutes, and each enforced call needs a signed, single-use boundary decision that lasts seconds (15 by default, 30 at most).
How Oathera helps
Oathera Agent Enforcement refuses unconfigured tools when its default-deny setting is on, and unknown tools and arguments outside an allow-list always. Clearance is the lower of what the agent requests and what its evidence supports. Revoke one agent without touching the others.
Oathera does not verify people, judge model output, inspect or rewrite prompts, or replace your identity provider. Your identity provider and proofing sources do the first; Oathera is the layer under them for agents.
FAQ
What is blast radius for an AI agent?
The extent of damage one compromised or misled agent can cause with the access it holds.
How do you fix over-privileged service accounts?
Replace the shared account with per-agent identity and a narrow boundary for each agent, enforced on every call.
What is just-in-time access for agents?
Authority granted for the operation at hand and not held in advance. Oathera issues a single-use decision per enforced call.
Can I limit one agent without affecting others?
Yes. Each agent has its own identity, so revoking or narrowing one leaves the rest unchanged.
Related: Enforce least privilege for an AI agent · Operational boundaries, enforced at runtime · Revoke an AI agent's access
Become a design partner Watch the simulator More guides
← Back to Learn