{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-manifest-replay-attacks-from-surviving-mcp-capability-re-attestation",
  "title": "Which invariants prevent manifest replay attacks from surviving MCP capability re-attestation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to MCP servers whose tool manifests are signed and whose capabilities are attested by a verifier that caches or reuses prior attestation state across manifest updates. Does not apply to stateless per-request verification where no attestation token is ever reused or persisted.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-manifest-replay-attacks-from-surviving-mcp-capability-re-attestation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-manifest-replay-attacks-from-surviving-mcp-capability-re-attestation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-manifest-replay-attacks-from-surviving-mcp-capability-re-attestation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 820,
    "python_slice_tokens": 152,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *signature validity* and *manifest freshness*. A signed tool manifest can be cryptographically valid while being a replay of a previously attested manifest. Verification of the signature alone proves only that some trusted key signed *some* manifest — not that this manifest is the current one bound to the attested capabili...",
    "what_was_observed": "A verifier accepted a manifest whose signature verified against the publisher key but whose embedded `manifest_digest` did not match the digest of the manifest body it accompanied. Because the verifier checked signature-over-manifest and attestation-token-validity as two independent predicates, an attacker could pair a fresh, legitimately signed attestation token (obtained for an old capability set) with a modified m...",
    "condition_of_validity": "The failure requires all of: (1) attestation tokens are cached or reused across manifest updates; (2) signature verification and capability comparison are performed as independent checks rather than as a single bound predicate; (3) the attestation epoch is not monotonic per publisher; and (4) no digest cross-check exists between the token's claimed manifest ...",
    "decision_boundary": "Treat a manifest as attested **only if** `token.manifest_digest == sha256(canonical(manifest_body))` AND `token.capabilities == manifest_body.capabilities` AND `token.epoch > last_seen_epoch[publisher]`. If any predicate is false, reject the manifest and force a full re-attestation rather than falling back to signature-only acceptance. Do not accept \"signatu...",
    "operational_effect": "Verifiers that enforce the bound predicate reject replayed manifests at the digest-comparison step, before any capability is granted. Verifiers that check predicates independently will grant capabilities from the manifest body while believing they validated the token — silently expanding the attack surface. The correction is to collapse the three checks into..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "33c2f1450c468a682678f53d8f9a432da28aaf5ad4a979726110096cf2d73651",
    "verified_classes": [
      "ManifestReplayError",
      "AttestationEpochError"
    ],
    "verified_functions": [
      "canonical_digest",
      "verify_attestation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AttestationEpochError",
      "ManifestReplayError"
    ],
    "sample_fail_closed_invariants": [
      "token missing publisher identity",
      "token capability set does not match manifest body capability set"
    ],
    "stdlib_dependencies": [
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
