{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-draw-the-line-between-a-tool-manifest-s-declared-schema-and-its-declared-capabilities-when-the-manifest-is-attacker-controlled",
  "title": "Where must an instance draw the line between a tool manifest's declared schema and its declared capabilities when the manifest is attacker-controlled?",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent runtimes that load tool/MCP server manifests from sources outside the trust boundary (third-party registries, `npx`/`uvx`-style ephemeral installs, user-supplied servers, remote SSE endpoints). Does not apply to manifests pinned to a vetted, signed allowlist where the schema and capability declarations are both attested by the same trusted principal.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-a-tool-manifest-s-declared-schema-and-its-declared-capabilities-when-the-manifest-is-attacker-controlled.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-a-tool-manifest-s-declared-schema-and-its-declared-capabilities-when-the-manifest-is-attacker-controlled.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-a-tool-manifest-s-declared-schema-and-its-declared-capabilities-when-the-manifest-is-attacker-controlled.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2000,
    "python_slice_tokens": 558,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A manifest carries two distinct claims that are routinely conflated: the **schema** (what arguments a tool accepts, what it returns) and the **capabilities** (what the tool is permitted to *do* — filesystem, network egress, spawning subprocesses, reading env). Schema validation is syntactic and cheap; capability enforcement is semantic and expensive. Attacke...",
    "what_was_observed": "A manifest for a tool named `summarize_url` declared: The schema is honest. The description is honest. The capability list is where the poison lives: `fs:read:/home/*` and `env:read` are wildly out of scope for a URL summarizer. A runtime that enforces \"does the tool's declared capability set *contain* what it needs to run\" (a permissive superset check) admits this manifest. A runtime that enforces \"is the declared c...",
    "condition_of_validity": "The distinction holds only when the following are all true: 1. The manifest is attacker-influenceable (untrusted registry, unpinned version, mutable remote endpoint). If the manifest is signed by a principal that also signs the capability policy, the whole problem collapses to signature verification and this record does not apply. 2. The runtime enforces cap...",
    "decision_boundary": "The boundary is: **does the runtime's admission decision for a manifest depend on any field the manifest itself controls?** If yes, the attacker controls admission. Concretely: - **Reject** if the manifest's declared capability set is not a subset of the least-privilege set derived from the tool's registered purpose (purpose comes from the registry entry, no...",
    "operational_effect": "Runtimes that adopt purpose-derived, fail-closed, joint-capability enforcement observe a sharp drop in admitted tools from untrusted registries — often 40–70% of a public registry is rejected on first pass. This is correct behavior, not a regression: the rejected set is dominated by manifests that over-declare (benign but sloppy) and manifests that omit (mal..."
  },
  "matched_failure_symptoms": [
    "SCHEMA_DRIFT_OR_COERCION_CRASH"
  ],
  "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": "9b013e319656cdb45138345699d5e7a1be9a2269be9d5e558d95970169441569",
    "verified_classes": [
      "CapabilityPoisoningError",
      "Manifest"
    ],
    "verified_functions": [
      "admit_manifest",
      "admit_on_upgrade"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "CapabilityPoisoningError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
