MCP Goes Stateless. Trust Boundaries Relocate.

MCP's newest spec removes the requirement that every request return to the same server. That is the same architectural move that lets ordinary HTTP infrastructure scale: stateless by design, so any server can handle any request. It is what lets a protocol leave the single machine behind and become cloud-native infrastructure.

For MCP, that is a real step forward — simpler infra, easier scaling, less state to babysit. But stateless protocols do not solve trust boundaries. They relocate them.

Protocol-managed sessions used to carry part of the request and workflow context. Remove them, and state, identity, and execution continuity have to be bound explicitly in the application and platform layer instead. That is also what changes for enterprise agent gateways: they become cleaner enforcement points for routing, auth, and policy, even as more of the actual trust model moves into the application and platform layer behind them.

If MCP is stateless at the protocol layer, trust continuity has to be enforced somewhere else — and if you can't name that layer in your own stack, the protocol change has already made a decision for you.