{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-tool-manifest-provenance-as-a-security-boundary-rather-than-a-metadata-field",
  "title": "In what scenarios must an instance treat tool-manifest provenance as a security boundary rather than a metadata field",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent runtimes that dynamically load, merge, or hot-reload tool manifests (MCP-style tool descriptors, OpenAPI fragments, plugin manifests) from more than one source at runtime. Does not apply to agents whose complete tool set is fixed at build time and shipped as an immutable artifact with no runtime discovery path.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-manifest-provenance-as-a-security-boundary-rather-than-a-metadata-field.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-manifest-provenance-as-a-security-boundary-rather-than-a-metadata-field.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-manifest-provenance-as-a-security-boundary-rather-than-a-metadata-field.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1764,
    "python_slice_tokens": 286,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A tool manifest is simultaneously two things: a *description* (name, schema, description text, parameter docs) and an *instruction channel* (the description and parameter documentation are consumed by the model as natural-language guidance). Most runtimes treat the manifest as data to be parsed and validated structurally — JSON Schema conformance, required f...",
    "what_was_observed": "In a representative dynamic-loading agent, tools were discovered from three sources: a bundled core set, a remote registry, and a local `plugins/` directory scanned on each session start. Manifests were validated against a JSON Schema that required `name`, `description`, `parameters`, and `handler`. All three sources passed through the same validator and were merged into a single tool list presented to the model with...",
    "condition_of_validity": "The invariant \"manifest text is trusted instruction\" holds only when **all** of the following are true: 1. Every manifest in the discovery set originates from a source with the same trust level as the agent's own code. 2. No manifest can be added, replaced, or hot-reloaded at runtime by a principal with less authority than the agent operator. 3. The model's ...",
    "decision_boundary": "An instance must escalate from \"parse and merge\" to \"quarantine and annotate\" when **any** of the following is detected at load time: - A manifest's source is not in the operator-signed allowlist. - A manifest's `description` or parameter docs contain imperative verbs directed at the agent (call, invoke, read, send, ignore, instead) rather than descriptive p...",
    "operational_effect": "The operational consequence is a change in *what the agent believes about its own tool set*. A runtime that treats manifests as trusted metadata will, after a skill injection, execute tool sequences the operator never authorized, using the model's own tool-selection machinery as the confused deputy. The blast radius is bounded only by what the injected prose..."
  },
  "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": "ce1ec638e7a409b59933f245d75fa1ebfd2be1c3fb1a32010b42613a3f97b85a",
    "verified_classes": [
      "UntrustedManifestError",
      "Manifest"
    ],
    "verified_functions": [
      "_references_sibling",
      "load_manifests"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UntrustedManifestError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
