AAK-TRUST-004: No deny rules defined
- Severity
- HIGH
- Category
- Trust Boundaries (
trust-boundary) - Scanner
agent_audit_kit/scanners/trust_boundary.py- Auto-fixable
- Yes.
agent-audit-kit fixcan apply it. - SARIF name
MissingDenyRules
What it detects
Settings file has permission allows but empty or missing deny rules. Defense-in-depth requires explicit deny rules for sensitive operations.
How to fix
Add deny rules for: file system operations outside project, network tools, credential-accessing tools.
agent-audit-kit fix can apply this change for you; add --dry-run to preview it.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-TRUST-004
Limitations
Fires when permissions.allow has entries and permissions.deny is empty or missing. Any non-empty deny list clears it, whatever it denies: Read(./docs/notes.md) beside Bash(curl:*) passes.
References
- OWASP MCP Top 10: MCP02:2025 (Privilege Escalation via Scope Creep)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-TRUST-02 (Missing Deny Rules)
- CSA AI Controls Matrix (AICM): IAM-02
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-TRUST-004.md: the page then shows that text, with the registry reference appended under it.