Agent connects to the database as an admin user
HighAV-PERM-005PermissionsCore packNew in 2.0
What it finds
The agent's database connection uses an administrator account (root, postgres, sa, admin).
Why it matters
Any SQL the agent runs — including injected or hallucinated queries — can read, change, or drop everything in every database.
What an attacker could do: One bad query could delete or leak the entire database.
How to fix it
Create a dedicated database user for the agent with access only to the tables and operations it needs (read-only where possible).
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
- AGENT_DB_SUPERUSER
- 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