Find an agent with broad tools, credentials, or workflow authority.
LLM06:2025
Excessive Agency
Excessive agency occurs when an AI system has more autonomy, permissions, tools, or action scope than the task requires.
Step 01
Input
Step 02
Model
Step 03
Tool / Data
Step 04
Impact
What it is
The agent can make too many decisions or execute too many actions without deterministic limits, approval gates, scoped credentials, or bounded workflow design.
Why it matters
An incorrect or manipulated instruction can become a sent message, deleted record, purchase or deployment when the agent has permission to perform it. Restricting that authority limits the damage a failed model instruction boundary can cause.
Failure path
One way this failure can develop.
Use this example to locate the input, permission or application check that would interrupt the sequence in your system.
Use prompt injection, misleading context, or normal conversation to steer the agent.
Make the agent take an action the user, owner, or business process did not intend.
Defenses
Controls worth checking.
Check where each control runs, who owns it and how you will test it again after a prompt, model or workflow change.
Reduce the action set
Give each workflow only the tools and scopes required for that job, with separate read, draft, write, send, delete, and deploy capabilities.
Add approval gates
Require human approval for destructive, external, financial, security-sensitive, or customer-visible actions.
Use deterministic policies
Enforce action rules outside the model so prompts cannot expand authority at runtime.
Signals and control gaps
- Agents holding broad OAuth scopes or long-lived service tokens.
- Write-capable tools available in read-only workflows.
- No separate approval path for send, delete, deploy, spend, or publish actions.
Questions for your team
- What can the agent do if every prompt-level control fails?
- Which tools can modify external state?
- Can a human see and approve the exact target before execution?