解决AI代理在生产环境调用工具时的三大安全短板。
Bridging Protocol and Production: Design Patterns for Deploying AI Agents with Model Context Protocol
- 提出三种新机制，分别处理身份传递、动态超时分配和错误语义结构化。
- 实测显示，未解决这些缺陷时，工具调用失败率高达37%。
- 适合需要高可靠性的企业级AI系统开发者参考。
Model Context Protocol（MCP）已实现超10,000个活跃服务器及每月9700万次SDK下载，但尚未规范AI代理在生产环境中安全使用外部工具的方法。本文通过与主流云服务商集成的大型企业部署实践，识别出三个关键协议缺失：身份传播、自适应工具预算分配与结构化错误语义。为此提出三项机制：（1）上下文感知代理协议（CABP），基于六阶段代理管道实现基于身份的请求路由；（2）自适应超时预算分配（ATBA），将序列化工具调用建模为异构延迟分布下的预算优化问题；（3）结构化错误恢复框架（SERF），提供机器可读的失败语义以支持代理自主纠错。论文归纳出五类生产故障维度（服务契约、用户上下文、超时、错误与可观测性），记录具体故障案例，并提供生产就绪检查清单。所有算法均形式化为可测试假设，具备可复现实验方法。实地观察表明，尽管MCP奠定良好协议基础，但可靠的工具集成仍需底层基础设施机制支撑。
原文摘要 · Abstract (English)
The Model Context Protocol (MCP) standardizes how AI agents discover and invoke external tools, with over 10,000 active servers and 97 million monthly SDK downloads as of early 2026. Yet MCP does not yet standardize how agents safely operate those tools at production scale. Three protocol-level primitives remain missing: identity propagation, adaptive tool budgeting, and structured error semantics. This paper identifies these gaps through field lessons from an enterprise deployment of an AI agent platform integrated with a major cloud provider's MCP servers (client name redacted). We propose three mechanisms to fill them: (1) the Context-Aware Broker Protocol (CABP), which extends JSON-RPC with identity-scoped request routing via a six-stage broker pipeline; (2) Adaptive Timeout Budget Allocation (ATBA), which frames sequential tool invocation as a budget allocation problem over heterogeneous latency distributions; and (3) the Structured Error Recovery Framework (SERF), which provides machine-readable failure semantics that enable deterministic agent self-correction. We organize production failure modes into five design dimensions (server contracts, user context, timeouts, errors, and observability), document concrete failure vignettes, and present a production readiness checklist. All three algorithms are formalized as testable hypotheses with reproducible experimental methodology. Field observations demonstrate that while MCP provides a solid protocol foundation, reliable agent tool integration requires infrastructure-level mechanisms that the specification does not yet address.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。