CrewAI agent can delegate to any crew member
LowAV-FW-004PermissionsFramework pack
What it finds
A CrewAI agent has delegation turned on, so it can hand tasks to any other agent in the crew.
Why it matters
Delegation lets an agent borrow other agents' tools. If one agent is manipulated, it can route work to a more powerful teammate.
What an attacker could do: A compromised agent could reach tools assigned only to other crew members.
How to fix it
Turn delegation off (allow_delegation=False) for agents that do not need it, and keep high-privilege tools on agents that cannot be delegated to by others.
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- CREWAI_OPEN_DELEGATION
- How it detects
- Looks for a specific risky pattern in the code or config.
- Confidence
- Definite: the risky setting is written plainly in the file.
- Scans
- Agent source using the named framework (LangChain, CrewAI, AutoGen, OpenAI Agents SDK, Claude Agent SDK, computer-use tools)
- OWASP LLM Top 10
- LLM08 - Excessive Agency
- NIST AI RMF
- GV-4.1
- SOC 2
- CC6.3
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.
Related checks
- Overly broad cloud IAM permissionsAV-PERM-003 · Critical
- AI workflow checks out untrusted PR code with secretsAV-PERM-007 · Critical
- Agent's Kubernetes account has cluster-adminAV-PERM-008 · Critical
- No permission or tool scope declaredAV-PERM-001 · High
- Unscoped delegation detectedAV-PERM-002 · High
- LangChain SQL agent with unrestricted database accessAV-FW-002 · High