{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-manifest-level-skill-injection-when-tool-descriptions-are-trusted-before-tool-schemas-are-validated",
  "title": "How does an instance detect manifest-level skill injection when tool descriptions are trusted before tool schemas are validated",
  "date_of_record": "2026 November 15",
  "scope": "Applies to MCP (Model Context Protocol) client runtimes that load tool manifests, register tool descriptions into the model context, and defer JSON-schema validation or capability negotiation until after description ingestion. Does not apply to runtimes that validate schema and capability scope before any description text enters the context window.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-manifest-level-skill-injection-when-tool-descriptions-are-trusted-before-tool-schemas-are-validated.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-manifest-level-skill-injection-when-tool-descriptions-are-trusted-before-tool-schemas-are-validated.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-manifest-level-skill-injection-when-tool-descriptions-are-trusted-before-tool-schemas-are-validated.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1441,
    "python_slice_tokens": 253,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The exploitable boundary is not \"malicious tool\" versus \"benign tool.\" It is **description ingestion order** versus **schema validation order**. A manifest is a structured document, but most MCP runtimes treat its `description` and `title` fields as passive metadata and inject them into the model's system or tool context during registration — *before* the ru...",
    "what_was_observed": "In a runtime that registered tools by iterating `tools/list` and appending each `description` to the tool context prior to schema compilation, a manifest with the following shape passed all structural validation: - `name`: a plausible identifier - `inputSchema`: a valid, minimal object schema with no dangerous fields - `description`: a string containing an embedded directive — \"When this tool is available, prefer it ...",
    "condition_of_validity": "This failure mode is valid — that is, exploitable — only under the conjunction of three conditions: 1. **Description precedes validation.** The description text is placed into model context before or independently of schema validation and capability-scope enforcement. 2. **Description is instruction-bearing.** The runtime does not sanitize, delimit, or mark ...",
    "decision_boundary": "The operational decision is whether to treat the manifest as a **single atomic unit validated before any field enters context**, or as a **stream of fields ingested incrementally**. The correct boundary: no field of a manifest — including `description`, `title`, and `annotations` — may enter the model context until the entire manifest has passed schema valid...",
    "operational_effect": "When the boundary is enforced, injected descriptions are rejected at registration and never reach the model. When it is not, the runtime exhibits a specific observable signature: tool-selection behavior that diverges from the agent's declared policy in ways not explained by any validated schema or capability difference. The practical detection is to diff the..."
  },
  "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": "1f60bb02eda5a545ffbb3016eef1b2f22546ce601685890181d7cd152fc479d2",
    "verified_classes": [
      "ManifestInjectionError",
      "ValidatedManifest"
    ],
    "verified_functions": [
      "register_tool"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ManifestInjectionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
