AAK-TRUST-007: No MCP server allowlist configured
- Severity
- MEDIUM
- Category
- Trust Boundaries (
trust-boundary) - Scanner
agent_audit_kit/scanners/trust_boundary.py- Auto-fixable
- Yes.
agent-audit-kit fixcan apply it. - SARIF name
NoMcpServerAllowlist
What it detects
The project's settings file has no enabledMcpjsonServers key while a root .mcp.json declares servers, so which of them Claude Code may start is decided by whoever answers the prompt rather than by the project.
How to fix
Configure enabledMcpjsonServers with explicit server names.
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-007
Limitations
Fires only when a settings file at the root of the scanned directory sits beside a root .mcp.json. A package directory that carries its own .claude/settings.json and .mcp.json (packages/web/) is not looked at. A present enabledMcpjsonServers key is the allowlist, an empty list included: [] approves no server, the strictest allowlist there is, and it is what aak fix writes, so the fix clears the finding. Through 0.6.24 an empty list fired too, and aak fix reported a change that cleared nothing. It reads the key, not the value: a list of names is the allowlist whether or not .mcp.json declares them.
References
- OWASP MCP Top 10: MCP09:2025 (Shadow MCP Servers)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-TRUST-04 (No Server Allowlist)
- 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-007.md: the page then shows that text, with the registry reference appended under it.