Skip to content

AAK-MCP-ATTEST-001: MCP server admitted without attestation

Severity
MEDIUM
Category
MCP Configuration (mcp-config)
Scanner
agent_audit_kit/scanners/mcp_config.py
Auto-fixable
No.
SARIF name
McpServerUnattested

What it detects

An MCP server entry in the agent/host config is dispatched without any of: a referenced signed clearance assertion, a /.well-known/mcp-clearance (or configured) URI, or a pinned trust root. Deny-by-default server admission is unenforced, so the server's self-declared tool list is implicitly trusted at dispatch time.

How to fix

Add an attestation (or clearance) field on the server entry pointing to a signed clearance document, expose it at /.well-known/mcp-clearance, and pin a trust_root in the host config that the host verifies before any tool dispatch. See Metere 2026, arXiv:2605.24248 — wire format, verification algorithm, and RFC-2119 conformance vectors.

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

agent-audit-kit scan . --rules AAK-MCP-ATTEST-001

Limitations

Fires on an entry of mcpServers (or servers in VS Code's .vscode/mcp.json) with a command or url that has none of 13 attestation keys (attestation, clearance, clearance_url, clearance_uri, clearance_document, clearancedocument, mcp_clearance, wellknown_clearance, well_known_clearance, trust_root, trustroot, trust_anchor, pinned_trust_root; any case, - for _) and no header named like MCP-Clearance or MCP-Attestation. A key only has to exist: "attestation": "" satisfies it, a top-level trust_root key silences every server in the file, and so does the text .well-known/mcp-clearance anywhere in the file; no clearance document or trust root is ever checked.

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