为AI代理跨协议委托提供可验证身份的统一认证方案
AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A
- 提出基于承诺的令牌链(IBCT),融合身份、权限衰减与溯源绑定
- 多跳场景下实测延迟仅增加2.35ms,对抗测试100%拦截异常委托
- 适合需要高可信代理协作的系统,如智能合约、自动化工作流
AI代理通过模型上下文协议(MCP)调用工具,并通过代理到代理(A2A)机制进行任务委托,但现有协议均无法验证代理身份。对约2000个MCP服务器的扫描显示,所有节点均缺乏身份认证。我们的调查显示,此前无实现方案能同时支持公钥可验证委托、持有者侧权限衰减、可表达的链式策略、跨MCP/A2A/HTTP的传输绑定以及以溯源为导向的完成记录。为此,我们提出调用绑定能力令牌(IBCT),一种将身份、衰减授权和溯源绑定融合于单一追加式令牌链的原语。IBCT支持两种传输格式:紧凑模式(签名JWT,适用于单跳)和链式模式(含Datalog策略的Biscuit令牌,适用于多跳)。我们提供了Python和Rust的参考实现,具备全语言互操作性。紧凑模式验证耗时0.049ms(Rust)和0.189ms(Python),在真实MCP-over-HTTP部署中引入0.22ms开销。在搭载Gemini 2.5 Flash的真实多代理部署中,AIP仅增加2.35ms延迟(占端到端总延迟的0.086%)。对抗评估在600次攻击尝试中实现100%拒绝率,其中两类攻击(委托深度越界、通过空上下文规避审计)仅由AIP的链式委托模型识别,传统未签名或普通JWT部署无法检测。
原文摘要 · Abstract (English)
AI agents increasingly call tools via the Model Context Protocol (MCP) and delegate to other agents via Agent-to-Agent (A2A), yet neither protocol verifies agent identity. A scan of approximately 2,000 MCP servers found all lacked authentication. In our survey, we did not identify a prior implemented protocol that jointly combines public-key verifiable delegation, holder-side attenuation, expressive chained policy, transport bindings across MCP/A2A/HTTP, and provenance-oriented completion records. We introduce Invocation-Bound Capability Tokens (IBCTs), a primitive that fuses identity, attenuated authorization, and provenance binding into a single append-only token chain. IBCTs operate in two wire formats: compact mode (a signed JWT for single-hop cases) and chained mode (a Biscuit token with Datalog policies for multi-hop delegation). We provide reference implementations in Python and Rust with full cross-language interoperability. Compact mode verification takes 0.049ms (Rust) and 0.189ms (Python), with 0.22ms overhead over no-auth in real MCP-over-HTTP deployment. In a real multi-agent deployment with Gemini 2.5 Flash, AIP adds 2.35ms of overhead (0.086% of total end-to-end latency). Adversarial evaluation across 600 attack attempts shows 100% rejection rate, with two attack categories (delegation depth violation and audit evasion through empty context) uniquely caught by AIP's chained delegation model that neither unsigned nor plain JWT deployments detect.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。