AAK-AZURE-MCP-001
Azure MCP server consumed without authentication
| Field | Value |
|---|---|
| Severity | HIGH |
| Category | MCP_CONFIG |
| Shipped | v0.3.5 (2026-04-25) |
| Scanner | agent_audit_kit/scanners/supply_chain.py (extension) |
| CWE | CWE-306 (Missing Authentication for Critical Function) |
| OWASP MCP | MCP07:2025 (Insufficient Authentication & Authorization) |
| OWASP Agentic | ASI03 (Identity and Privilege Abuse) |
| AICM | IAM-01, IAM-16 |
| CVE | CVE-2026-32211 (CVSS 9.1; write-up on dev.to) |
| Incident | MSRC-2026-04-03-AZUREMCP |
What it catches
An .mcp.json, .cursor/mcp.json, .vscode/mcp.json,
.amazonq/mcp.json, mcp.json, or any file under .azure-mcp/
references an Azure MCP endpoint (host matches *.azure.com,
*.azurewebsites.net, *.cognitiveservices.azure.com,
*.openai.azure.com, or contains azure-mcp / azure_mcp) without
one of the recognised auth markers:
Authorizationheaderclient_certificate/client_cert/mtlsmarkerapi_key/x-functions-keyfieldDefaultAzureCredential/ManagedIdentity/WorkloadIdentityazure_ad/bearer_token
CVE-2026-32211 documented the server-side default of zero auth on the MCP endpoint; downstream agents must add a transport-layer credential or risk session-hijack / tool-impersonation by anyone reachable on the network.
What it does NOT catch
- Server-side AAK does not currently scan the Azure MCP server's own config — the consumer-side check above is the load-bearing detection. Server operators should bump to the patched version per the MSRC advisory.
.mcp.jsonfiles that build the auth header at runtime viaheaders_from_env: trueor similar non-standard schemes — the scanner cannot prove a header arrives at request time. Add an explicitAuthorizationplaceholder in the JSON to silence.
Remediation
Add an Authorization header sourced from a managed identity token,
mTLS cert, or vault-issued API key:
{
"mcpServers": {
"azure-data": {
"url": "https://my-mcp.azurewebsites.net/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer ${AZURE_AD_TOKEN}"
}
}
}
}
For production deployments, prefer Azure-AD managed identities or workload-identity federation over static API keys.
Registry reference
This section is generated from the rule registry (agent_audit_kit/rules/builtin.py) when the documentation is built, so it follows the scanner. The rest of the page is hand-written; where the two disagree, the registry is what runs.
- Severity
- HIGH
- Category
- MCP Configuration (
mcp-config) - Scanner
agent_audit_kit/scanners/supply_chain.py- Auto-fixable
- No.
- SARIF name
AzureMcpMissingAuth
What it detects
An .mcp.json / .azure-mcp/ config references an Azure MCP server endpoint without an Authorization: header, mTLS client cert, or Azure-AD token-exchange. CVE-2026-32211 (CVSS 9.1) documented the server-side default of no auth on the MCP endpoint; downstream agents must add a transport-layer credential or risk session-hijack / tool-impersonation by anyone reachable on the network.
How to fix
Add an Authorization header with an Azure-AD token (preferred), an mTLS client certificate, or a static API key obtained from a secrets vault. Azure-AD managed identities or workload identity federation are the documented production paths.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-AZURE-MCP-001
Limitations
Decides per file, not per server: it reads .mcp.json, .cursor/mcp.json, .vscode/mcp.json, .amazonq/mcp.json, mcp.json and .azure-mcp/**/*.json, and fires on one that contains an Azure host (.azure.com, .azurewebsites.net, .cognitiveservices.azure.com, .openai.azure.com) or the word azure-mcp (also azure_mcp, azuremcp), and none of Authorization, mtls, DefaultAzureCredential, ManagedIdentity, WorkloadIdentity, client_cert (also client-cert, clientcert), api_key (also api-key, apikey), azure_ad (also azure-ad, azuread), bearer_token or x-functions-key anywhere in the file, in any case. An unauthenticated Azure server beside any server that carries an Authorization header passes. A file over 2 MB is not read.
References
- CVE: CVE-2026-32211
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
- Incidents and advisories: MSRC-2026-04-03-AZUREMCP
- CSA AI Controls Matrix (AICM): IAM-01, IAM-16