Skip to content

AAK-MCP-TUNNEL-002: MCP Tunnels proxy: HTTPS upstream without trust anchor

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

What it detects

An MCP Tunnels gateway-proxy config declares one or more https:// upstreams under routes: but sets neither upstream.tls.ca_file nor upstream.tls.include_system_cas: true. Quoting the reference: "otherwise the proxy has no trust anchor for the upstream certificate." Without a trust anchor the proxy will fail closed at best or accept a man-in-the-middle's certificate at worst, depending on the proxy build.

How to fix

Add upstream.tls.ca_file: <path> pointing at a CA bundle that issued the upstream certificates, OR set upstream.tls.include_system_cas: true to trust the system CA bundle. See https://platform.claude.com/docs/en/agents-and-tools/mcp-tunnels/reference#proxy-configuration.

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

agent-audit-kit scan . --rules AAK-MCP-TUNNEL-002

Limitations

Fires on an https:// route in a proxy config (a YAML file with tunnel_domain and routes) when neither upstream.tls.ca_file nor upstream.tls.include_system_cas is set. Only a file named config, proxy or values (.yaml or .yml), or one under a directory named tunnel, gateway, mcp-tunnel, mcp-tunnels, mcp-gateway, mcp_tunnel or mcp_gateway, is read, so the same configuration saved as deploy/proxy-prod.yaml is not.

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