Agent requests very broad OAuth scopes
HighAV-PERM-004PermissionsCore packNew in 2.0
What it finds
The agent asks for full-account OAuth scopes such as GitHub "repo", Google Drive / Gmail full access, or Microsoft "*.ReadWrite.All".
Why it matters
The token can do far more than the agent's task. If the agent is manipulated or the token leaks, everything in that account is exposed.
What an attacker could do: Full read/write access to the connected account's repos, mail, or files.
How to fix it
Request the narrowest scopes (e.g. drive.file, gmail.readonly, a fine-grained GitHub token for one repo).
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
- OVERBROAD_OAUTH_SCOPES
- 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
- Any text-based agent source or configuration (JS/TS/Python/JSON/YAML)
- OWASP LLM Top 10
- LLM08 - Excessive Agency
- NIST AI RMF
- GV-4.1
- SOC 2
- CC6.1, 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