# LLM06 - Excessive Agency

> LLM system granted too much autonomy or overly permissive access to tools and APIs.

- **Category**: Owasp Llm
- **Subcategory**: top10_2025
- **Canonical URL**: https://designpattern.fyi/owasp_llm/llm06_excessive_agency/

---

## Description
'**Intent**: Limit the actions an LLM-based system can perform to only what is necessary for its intended function.

**Context**: LLM-based systems connected to tools, APIs, or databases may perform unintended actions if granted excessive permissions. This can lead to data modification, financial transactions, or system changes.

**Solution**: Apply least privilege to all tool and API access. Require human-in-the-loop for high-impact actions. Implement action allowlists. Rate-limit tool calls. Log all actions for audit. Use confirmation workflows.'



## Use Cases
Use when connecting LLMs to external tools, APIs, databases, or any system that can perform real-world actions.





## Trade-offs


### Advantages

- Prevents unintended actions

- Limits blast radius of errors

- Enables accountability

- Supports compliance requirements




### Considerations & Drawbacks

- Reduces automation capabilities

- Human-in-the-loop slows workflows

- Permission granularity is complex







---
**Reference**: [Original Source](https://genai.owasp.org)