Summary
arXiv:2602.11327 — Security Threat Modeling for Emerging AI-Agent Protocols: A Comparative Analysis of MCP, A2A, Agora, and ANP (February 11, 2026)
Systematic security threat model covering four agent protocols. Key attack vectors directly applicable to Zeph:
MCP threats:
Tool shadowing : malicious server registers tools with names overlapping legitimate ones; client selects wrong tool
Tool poisoning via description injection : malicious instructions embedded in description field influence model behavior
Credential exfiltration : tools with filesystem/network access can leak vault secrets if execution is not sandboxed
A2A threats:
Coarse-grained token privilege escalation : A2A tokens issued for one agent can be replayed to another agent in the same trust domain
Agent impersonation : without cryptographic identity, rogue agents can claim legitimate identities during task delegation
Gap in Zeph:
zeph-mcp: shadowing detection added (security(mcp): tool poisoning detection and per-tool trust metadata (#2459, #2420) #2472 ) but no cross-server deduplication of tool names; a malicious second server can shadow a tool from a trusted first server
zeph-a2a: token scope is not per-task; a token obtained for subtask A can be presented for subtask B in the same session
No cryptographic agent identity verification in either zeph-mcp or zeph-a2a
Proposed Improvements
Cross-server tool name collision detection in McpManager — flag or reject duplicate tool names across servers with different trust levels
Per-task token scoping in A2A delegation — bind token to task ID + agent endpoint
Optional agent identity signature verification (JWK/Ed25519) in A2A handshake
References
Summary
arXiv:2602.11327 — Security Threat Modeling for Emerging AI-Agent Protocols: A Comparative Analysis of MCP, A2A, Agora, and ANP (February 11, 2026)
Systematic security threat model covering four agent protocols. Key attack vectors directly applicable to Zeph:
MCP threats:
descriptionfield influence model behaviorA2A threats:
Gap in Zeph:
zeph-mcp: shadowing detection added (security(mcp): tool poisoning detection and per-tool trust metadata (#2459, #2420) #2472) but no cross-server deduplication of tool names; a malicious second server can shadow a tool from a trusted first serverzeph-a2a: token scope is not per-task; a token obtained for subtask A can be presented for subtask B in the same sessionzeph-mcporzeph-a2aProposed Improvements
McpManager— flag or reject duplicate tool names across servers with different trust levelsReferences