Governed MCP retrieval and release-flow guide

Synthetic worked example

Meter one execution and replay it safely

How can an agent retry without consuming a second licensed unit?

An identical request reuses the original execution identity and bytes; changed material under the same request ID is refused.

Starting inputs

An active grant with quota

A stable client request ID

Canonical tool arguments

An active release

Ordered execution

Work the example

  1. 1

    Reserve quota atomically before delivery.

  2. 2

    Persist the request and release digests with the execution.

  3. 3

    Return the licensed projection.

  4. 4

    On retry, revalidate grant and active release.

  5. 5

    Return identical bytes without a second reservation.

Expected outputs

  • One quota unit consumed
  • One execution identity
  • Byte-identical idempotent replay

Verification checks

  • The first call consumes one unit.
  • The exact replay consumes zero additional units.
  • Expired grants refuse even on replay.

Fail closed

Refusal conditions

  • Quota is checked after delivery.
  • A replay bypasses revocation.
  • A changed selector reuses the stored result.

Digest-bound public fixture

Check the expected state

This fixture contains synthetic operational fields only. Its digest establishes fixture integrity, not scientific truth or a completed commercial transaction.

{
  "artifactKind": "licensed-delivery",
  "schemaVersion": "maha-licensed-evidence/1.0",
  "input": {
    "requestId": "synthetic-replay-001",
    "calls": 2,
    "materialInputsEqual": true
  },
  "expected": {
    "executions": 1,
    "quotaUnitsConsumed": 1,
    "secondOutcome": "idempotent-replay"
  },
  "artifactSha256": "sha256:459c8c5fc87d0991415019d5caed18597b3dae1537239eb8f1d7a99aa5467776"
}