Unverified50% confidenceFactExact time
The ExtMCP interface is defined in ext_mcp.proto and contains two RPCs: CheckRequest and CheckResponse, each of which returns either allow, a modified version, or a rejection with an error.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedExtMCP is wired in via an mcpGuardrails policy block, in which methods: tools/call: full means both hooks run for tools/call: CheckRequest before the filesystem server sees the call, and CheckResponse after it responds.72% similarUnverifiedExtMCP is an external gRPC service that agentgateway calls before a tools/call request reaches the upstream server, and calls once more after the response returns.68% similarVerifiedMCP基于JSON-RPC 2.0协议构建，支持请求-响应和通知两种消息模式63% similarUnverifiedA /mcp reconnect all command has been added for MCP, enabling a single retry of all MCP servers that have failed to connect or require authentication.63% similarUnverifiedThe team ultimately decided to bypass MCP's JSON-RPC handshake for database drivers and instead execute directly against database tables to keep the Agent alive.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1047873API
curl https://kongchang.com/api/v1/knowledge/claims/1047873MCP
get_claim(id=1047873)