LLM06 excessive agency: which controls work and which do not?
OWASP LLM06 excessive agency comes from too many functions, permissions and autonomy. Controls that prevent it, and controls that only limit the damage.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
OWASP LLM06 excessive agency comes from too many functions, permissions and autonomy. Controls that prevent it, and controls that only limit the damage.
Excessive agency means an AI agent can do more than it should. Use this checklist to cut tools, narrow permissions, add approvals and check downstream.
Treat model output as untrusted input. Encode it for each destination, parameterize queries and limit privileges. Prompt wording alone is not a control.
Improper output handling is classic injection with a model in the middle. See how OWASP LLM05 maps to secure development, logging and validation duties.
Test for LLM04 by checking where data and model files came from, comparing behavior against a fixed evaluation set, and watching training for anomalies.
LLM04 covers tampered training, fine-tuning and embedding data, plus poisoned model files. Learn the documented examples and the controls OWASP recommends.
OWASP LLM03:2025 covers models, adapters, datasets and packages you did not build. Here is a concrete list of events to log and the alerts worth wiring up.
LLM03 covers risk from packages, models, adapters and data you did not build. See the incidents OWASP cites and the controls that cut the exposure.
LLM03 supply chain risk lines up with NIST SP 800-161, the NIST AI RMF and EU AI Act Articles 17 and 25. See the mapping and the evidence to keep for each.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.