{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-manifest-provenance-from-manifest-content-in-mcp-tool-injection-defenses",
  "title": "How should an instance Distinguish Manifest Provenance from Manifest Content in MCP Tool Injection Defenses",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agents that discover tools dynamically through MCP registries, tool manifests, or plugin descriptors where the tool's declared capability set is used to gate execution. Does not apply to statically compiled tool bindings whose signatures are frozen at build time and whose provenance is cryptographically pinned to the host binary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-manifest-provenance-from-manifest-content-in-mcp-tool-injection-defenses.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-manifest-provenance-from-manifest-content-in-mcp-tool-injection-defenses.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-manifest-provenance-from-manifest-content-in-mcp-tool-injection-defenses.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1497,
    "python_slice_tokens": 252,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure that recurs is a conflation between *what a manifest claims* and *who is entitled to make that claim*. A manifest is a data structure: it carries a name, a version, a description, a set of input schemas, and a list of the tools it exposes. Every field in that structure is attacker-controlled if the transport that delivered it is not authenticated...",
    "what_was_observed": "In a controlled registry-poisoning exercise, a malicious MCP server registered under a name one edit-distance from a high-trust server (`filesystem-read` vs `filesystem-reads`) and published a manifest whose tool list was a strict subset of the legitimate server's — deliberately *fewer* tools, all benign-looking, all passing the content allow-list. The agent's discovery layer selected it because the registry index re...",
    "condition_of_validity": "The distinction holds — content validation is insufficient and provenance validation is required — only under the following conditions: 1. Tool discovery is dynamic (registry lookup, remote manifest fetch, or plugin enumeration at runtime), so the agent does not have a compile-time-fixed tool set. 2. The orchestrator incorporates manifest-derived text (descr...",
    "decision_boundary": "The operational rule: - **Accept a manifest only if** (a) its signature chains to a registry root the agent independently trusts, (b) the signing key matches the *expected publisher identity* for that tool name (not merely *a* trusted publisher), and (c) the manifest's revocation status is checked against a freshness-bounded revocation list, not just its sig...",
    "operational_effect": "Enforcing the provenance/identity binding converts the attack from \"silent tool substitution\" into \"loud discovery failure.\" The observable effect is that discovery becomes fail-closed: an agent that cannot confirm publisher-to-name binding refuses to load the tool rather than loading it with reduced capability. This is operationally more disruptive — it sur..."
  },
  "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": "b3b531142167b743335141296cfc9f3019b25ab185ff4b466e1fe46706e46b75",
    "verified_classes": [
      "ManifestProvenanceError",
      "Manifest"
    ],
    "verified_functions": [
      "admit_manifest",
      "admit_manifest_text",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "ManifestProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
