AAK-SHELL-DEFAULT-PROFILE-001: Command-executing tool is reachable in the default tool profile
- Severity
- HIGH
- Category
- MCP Configuration (
mcp-config) - Scanner
agent_audit_kit/scanners/quoted_shell_interp.py- Auto-fixable
- No.
- SARIF name
ShellToolDefaultProfile
What it detects
A tool that reaches a command-execution sink is registered in the server's default profile, with no opt-in flag, environment gate, or profile membership standing between a freshly connected MCP client and the sink. This is the condition that moved both August 2026 shell CVEs from theoretical to high: no non-default configuration was needed, which is what the PR:N in their CVSS vectors records. Fires only for tools that already reach a command sink, so it qualifies a real finding rather than complaining about every server that runs commands.
How to fix
Move command-executing tools behind an explicit opt-in — an AAK_ENABLE_* environment gate, a named non-default tool profile, or a CLI flag — so that reaching the sink requires a deliberate operator decision rather than the default install.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-SHELL-DEFAULT-PROFILE-001
Limitations
Reads the registration site in the same file as the tool. A gate applied by a loader in another module is not seen.
References
- CVE: CVE-2026-55157, CVE-2026-55071
- 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-TOOL-02
- Incidents and advisories: GHSA-49mq-fc6q-3h46, GHSA-49m4-vp58-wgc9
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-SHELL-DEFAULT-PROFILE-001.md: the page then shows that text, with the registry reference appended under it.