Skip to content

AAK-MCP-SIDECAR-NOAUTH-001: MCP server binds an unauthenticated sidecar HTTP surface

Severity
HIGH
Category
MCP Configuration (mcp-config)
Scanner
agent_audit_kit/scanners/mcp_sidecar_http.py
Auto-fixable
No.
SARIF name
McpSidecarNoAuth

What it detects

A process that registers MCP tools also binds an HTTP listener whose routes carry no authentication dependency or middleware (CWE-306, Missing Authentication for a Critical Function). The MCP transport itself may be authenticated or stdio-only, but the sidecar dashboard / status API / debug UI beside it is not, and it is backed by the same process state and the same operator credentials. Binding to loopback is not an authorization boundary: the listener is reachable by DNS rebinding from any page the operator visits, and by any co-located SSRF on the host. Distinct from AAK-MCP-HTTP-NOAUTH-SERVER-001, which covers the MCP endpoint itself bound to a non-loopback interface or serving wildcard CORS; this rule covers the second listener, on loopback, that the threat model forgot.

How to fix

Put authentication on the sidecar's routes, not just on the MCP transport. A bearer token or API-key header checked in middleware is enough, and unlike a loopback bind it also survives DNS rebinding. If the surface exists only for local debugging, gate it behind an explicit opt-in flag that is off by default.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-SIDECAR-NOAUTH-001

Limitations

Detects the listener and the absence of an auth marker in the same file. An auth check applied from a separate middleware module that this file never references will read as absent.

References


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-MCP-SIDECAR-NOAUTH-001.md: the page then shows that text, with the registry reference appended under it.