AgentCollusionAI security startup
News

Field note 24 · MCP & tools

Stateless MCP Moves State Into the Evidence Layer

Removing transport sessions improves scalability but forces systems to preserve task and principal continuity elsewhere.

By Kotaro OKUYAMA2 min read
Editorial illustration for Stateless MCP Moves State Into the Evidence Layer

Stateless transport needs explicit correlation identifiers and durable provenance outside the connection.

Why this question matters

The MCP 2026-07-28 release emphasizes stateless architecture so gateways, rate limiters, and distributed infrastructure can scale requests. Connection-local state can no longer serve as a reliable shortcut for identifying one workflow or principal.

This is healthy architectural pressure. Every operation should carry or reference the minimum context needed for policy and audit. The danger is inventing opaque correlation IDs that join events operationally but cannot explain delegation or purpose.

Signals worth observing

  • Requests share no durable task or principal reference.
  • Load balancing creates several incomplete traces for one outcome.
  • Correlation identifiers can be chosen or reused by untrusted agents.

Practical control direction

  1. Use server-issued, integrity-protected task references.
  2. Join tool calls to A2A task and delegation evidence.
  3. Separate observability identifiers from authorization secrets.
AgentCollusion lensA stateless protocol can still support stateful accountability when the relationship graph is explicit.

Sources and further reading

Next field note: Task Cancellation Is a Security Control