AAK-A2A-011: A2A tokens not anti-replay protected
- Severity
- MEDIUM
- Category
- A2A Protocol (
a2a-protocol) - Scanner
agent_audit_kit/scanners/a2a_protocol.py- Auto-fixable
- No.
- SARIF name
A2aReplayable
What it detects
An A2A flow accepts tokens without nonce, timestamp, or jti checks, allowing captured messages to be replayed. Replay on trust chains is one of the OWASP ASI07 (Insecure Inter-Agent Communication) examples.
How to fix
Declare replay protection in the card's tokens block with jti, nonce, require_jti or replay_window, and enforce it: put jti or nonce and iat/exp claims in every token and reject a repeated jti inside the replay window.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-A2A-011
Limitations
Checks that the tokens block contains a jti, nonce, require_jti or replay_window key and does not look at its value, so "require_jti": false or "replay_window": 0 satisfies it. A card with no tokens block, or an empty one, is not examined.
References
- OWASP Agentic Top 10: ASI07 (Insecure Inter-Agent Communication)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-A2A-08
- CSA AI Controls Matrix (AICM): IAM-01
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-011.md: the page then shows that text, with the registry reference appended under it.