Notifications
Clear all
Topic starter
06/09/2026 9:34 am
TL;DR: Replacing JSON-RPC with gRPC for MCP creates stricter schema guarantees, native mutual authentication, and better streaming resilience for enterprise AI agents, according to FireCompass. The key issue is that dynamic, loosely typed context handling weakens both security and reliability when agents touch sensitive systems, while Google Cloud’s support validates the direction.
NHIMG editorial — based on content published by FireCompass: Before Google Cloud Backed gRPC for MCP, FireCompass Built It for Our AI Agents
By the numbers:
- By moving to a binary encoding format, message sizes shrink dramatically, up to 10x smaller.
- Payload efficiency improved by 75%+ after FireCompass replaced JSON-RPC with Protobufs.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: What breaks when MCP relies on loose JSON-RPC payloads for AI agents?
A: Loose JSON-RPC payloads weaken trust boundaries because the server must interpret commands before it can validate them.
Q: Why do AI agent transport decisions matter for identity governance?
A: Transport decisions matter because they determine where identity is verified, where input is trusted, and where policy can be enforced.
Q: What signs indicate an MCP-based agent architecture is failing security review?
A: Common warning signs include dynamic payload parsing, missing mutual authentication, no schema enforcement, and unlimited tool-call retries.
Practitioner guidance
- Move agent transport into the control model Document MCP transport as part of the identity architecture, not just the integration stack.
- Require schema validation before execution Reject malformed or ambiguous agent payloads at the serialization layer so tool calls cannot be interpreted opportunistically.
- Bind agent sessions with mutual authentication Use mTLS and token-based verification between agents and tools so both sides prove identity before context is shared.
What's in the full article
FireCompass's full blog post covers the operational detail this post intentionally leaves for the source:
- Side-by-side architecture notes on the JSON-RPC to gRPC rewrite for Switchblade
- Benchmark methodology behind the reported payload, latency, and parsing gains
- Implementation details for mTLS, JWT or OAuth integration, and bidirectional streaming
- The article's examples of how schema enforcement blocks malformed tool calls before execution
👉 Read FireCompass's analysis of gRPC transport for MCP and AI agents →
gRPC for MCP: what it changes for AI agent security teams?
Explore further
06/09/2026 9:34 am
Schema-first transport is becoming a governance control, not just an engineering preference. Once AI agents can invoke tools directly, the structure of the protocol determines how much trust the system can safely extend. Loose message formats and implicit parsing create governance ambiguity because policy enforcement happens after interpretation instead of before it. The implication is that identity teams must treat MCP transport choices as part of the access architecture, not as an implementation detail.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: How should security teams govern AI agents that use service accounts and MCP tools?
A: Start with ownership, then add runtime attribution and containment. Security teams should know which human deployed the agent, which identity the agent uses, what tools it can invoke, and when to revoke access. If the agent can chain tool calls or spawn sub-agents, governance must cover those paths as well, not just the initial login.
👉 Read our full editorial: gRPC for MCP raises the security bar for enterprise AI agents
