MCP | Thomas Talks AI

A Claude Code transcript passes through five independent evidence checks for identity, authority, durable effect, observation, and cleanup before a reviewer accepts the run

A Claude Code audit trail needs proof beyond the transcript

A Claude Code transcript can describe an MCP action without proving who was authorized, what committed, whether an independent read saw it, or what rollback left behind.

A Claude Code MCP write waits in a retry queue beyond its approval expiry, keeps the same operation ID, and is blocked by an execution-time authority check

Claude Code queued an approved MCP write. It ran after permission expired

A stable operation ID can stop duplicate MCP writes while still allowing an action after its approval expires. Recheck authority where the effect occurs.

A Claude Code MCP write passes through an acknowledgement gate, durable commit check, and independent read before a durability receipt is issued

Claude Code got a success receipt before the write was durable

An MCP tool can return success after accepting a write but before durable storage. Define acknowledgement levels, verify the committed version, and give Claude Code a durability receipt.

Two parallel Claude Code writes request operation IDs from one atomic identity ledger, which issues unique IDs and blocks collisions before MCP dispatch

Claude Code gave two parallel writes the same operation ID

Two parallel Claude Code tool calls can share an operation ID and corrupt retry evidence. Allocate identity centrally, bind it to intent, and reject collisions before dispatch.

Two Claude Code eval cases are separated by a reset gate that verifies a clean sandbox before the second case starts

Claude Code passed the eval because the previous case cleaned up for it

A Claude Code eval can pass only because an earlier case left the sandbox in a helpful state. Give every case a fresh environment, a state fingerprint, and a reset receipt.

A new Claude Code run is blocked because its pooled MCP session still carries the previous tenant context

Claude Code changed tenants. The MCP session did not.

A new Claude Code run selected the right tenant, but its pooled MCP session kept the previous tenant context. Bind every session to the authority it carries.

A Claude Code request for staging is blocked when the MCP gateway reveals that an adapter default would execute it against production

Claude Code asked for staging. The MCP adapter defaulted to production

A reviewer approved a staging MCP request, but the adapter filled an omitted environment with production. Authorize the normalized payload that will actually execute.

Claude Code course path from a convincing demo to a governed run and production evidence

My Claude Code production agents course is live

My new practical Leanpub course turns the production engineering behind Claude Code agents into labs, assessments, capstones, and a production-readiness dossier.

A revoked Claude Code permission is blocked when the MCP gateway compares a cached allow decision with the current policy version and revocation epoch

Claude Code lost permission. The MCP cache still said allow

Revoking Claude Code access is useless if an MCP gateway keeps serving an old allow decision. Bind cached authorization to policy version, resource state, and a short expiry.

An approved Claude Code MCP call is stopped when a redirect changes the destination, then allowed only after scheme, host, port, TLS identity, and resolved network range match the transport binding

Claude Code approved one MCP server. The request went somewhere else.

An MCP approval can bind to a tool name while DNS, redirects, proxies, and service discovery send the request elsewhere. Pin the transport identity at dispatch time.