AAK-A2A-007: Agent impersonation risk
- Severity
- MEDIUM
- Category
- A2A Protocol (
a2a-protocol) - Scanner
agent_audit_kit/scanners/a2a_protocol.py- Auto-fixable
- No.
- SARIF name
AgentImpersonationRisk
What it detects
An A2A Agent Card lacks an 'id' or 'identity' field, or uses an HTTP endpoint, making it susceptible to agent impersonation attacks.
How to fix
Add a unique 'id' or 'identity' field to the Agent Card and use HTTPS endpoints.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-A2A-007
Limitations
Checks only that an id or identity key exists, not what it holds: "id": "" and "identity": null both satisfy it, and nothing looks for a signature or any other proof of the identity. The other condition, an http:// address in a top-level url, endpoint, baseUrl or base_url, does not look under additionalInterfaces. A URL that Node, requests and Rust's url crate read differently from curl, httpx and urlsplit, which keep a backslash inside the authority, is judged by the less safe of the two readings.
References
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI10 (Rogue Agents)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
- CSA AI Controls Matrix (AICM): IAM-04
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-A2A-007.md: the page then shows that text, with the registry reference appended under it.