{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-an-mcp-tool-call-despite-a-valid-capability-attestation",
  "title": "In what scenarios must an instance reject an MCP tool call despite a valid capability attestation",
  "date_of_record": "2026 November 15",
  "scope": "Applies to MCP (Model Context Protocol) servers that advertise capabilities via signed attestation documents and are consumed by an orchestrating agent that performs runtime integrity verification before each tool invocation. Does not apply to first-party, in-process tool registries where the tool implementation and the caller share an address space and a trust boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-an-mcp-tool-call-despite-a-valid-capability-attestation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-an-mcp-tool-call-despite-a-valid-capability-attestation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-an-mcp-tool-call-despite-a-valid-capability-attestation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1540,
    "python_slice_tokens": 222,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A capability attestation answers *\"what is this server permitted and configured to do?\"* — it is a statement about **authority and declared surface**. Runtime integrity verification answers *\"is the process I am about to call the same process the attestation describes, right now?\"* — it is a statement about **identity and current state**. The non-obvious fai...",
    "what_was_observed": "Across a set of third-party MCP providers, four recurring conditions produced a *valid attestation paired with an unsafe invocation*: 1. **Schema drift under a stable `tool_name`.** The provider published a new server build that widened an input schema (added an optional object field that the implementation then dereferenced unconditionally). The attestation's `schema_hash` covered the *published* schema, not the *se...",
    "condition_of_validity": "The attestation is a valid authorization to invoke **only when** all of the following hold simultaneously at the moment of the call: - The attestation is the **current** one for `provider_id` (not merely unexpired — re-fetch or compare against a monotonic version, do not trust cache TTL alone). - The **live target** presents a build digest and a served-schem...",
    "decision_boundary": "The boundary is between **attestation-valid** and **invocation-safe**. They coincide only under the four conditions above. The decision rule: - *Attestation invalid* → reject, unconditionally. - *Attestation valid but runtime challenge fails, times out, or returns a digest/schema/scope set that does not match* → **reject**, even though every signature check ...",
    "operational_effect": "When the boundary is enforced, third-party tool calls carry a per-invocation cost: one runtime challenge round-trip and one currency check against the provider's current attestation. This is the price of closing the gap between \"the provider said\" and \"the instance is.\" When it is not enforced, the system exhibits *attestation theater*: full cryptographic ce..."
  },
  "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": "aa03e21472632c83479bfe14a390e622798ba922f37fb0f2629f6d16d9873b58",
    "verified_classes": [
      "UnattestedInvocationError",
      "Attestation",
      "RuntimeProbe"
    ],
    "verified_functions": [
      "authorize_invocation"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "UnattestedInvocationError"
    ],
    "sample_fail_closed_invariants": [
      "no runtime challenge response; absence of proof is not proof",
      "schema drift: served schema does not match attested schema_hash"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
