An envelope, not an on-wire rewrite
IntentGate issues a signed recovery and inoculation envelope the runtime applies. It does not rewrite the HTTP or SSE context stream on the wire.
MCP firewall capability
Self-Healing Session Rewind
When a breaker trips or an anomaly is caught, the workflow does not have to crash. IntentGate issues a signed recovery-and-inoculation envelope that returns the session to a known-safe state and inoculates it against repeating the offending pattern—signed with the gateway key so the runtime can trust what it applies.
Trip, envelope, restored and inoculated
Recovery is a signed instruction the runtime applies, not a silent rewrite of the traffic underneath it.
Breaker or anomaly tripA circuit breaker fires or an anomaly is caught on the tool-call path.
Signed recovery + inoculation envelopeIssued by the gateway and signed with the gateway key so the runtime can verify it.
Session restored & inoculatedReturned to a known-safe state and hardened against repeating the offending pattern.
What the envelope carries
The envelope is a small, verifiable payload the runtime consumes. It records why it was issued and what safe state to return to.
Recovery
Return the session to a known-safe checkpoint instead of crashing the workflow.signed: gateway key↓ same signed envelope
Inoculation
A synthetic instruction that inoculates the session against repeating the pattern that tripped the control.pattern: offending call↓ verified, then applied
Applied by the runtime
The client verifies the signature and applies it; the issuance joins the hash-chained audit.audit: appendedHonest limits
Rewind is a signed recovery and inoculation envelope. It is deliberately not the on-wire re-stream proxy.
Not a re-stream or backlog proxy
Replaying and rewriting the context stream through a proxy is backlog, not shipping. Describing it as live would be overclaiming, so we do not.
Signed with the gateway key
The envelope is signed so the runtime can verify origin before applying it. A client that cannot verify the signature does not apply the recovery.
The runtime does the applying
The gateway issues; the client applies. Recovery depends on a runtime that consumes the envelope, which is why it is delivered as signed, verifiable state.
Related capabilities
Each control sits on the same MCP firewall decision path. Explore the neighbouring runtime capabilities.