{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-reject-a-dynamically-registered-mcp-capability-the-description-trust-boundary",
  "title": "When must an instance reject a dynamically registered MCP capability: the description-trust boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agents that load tool definitions from MCP servers at runtime, including servers reached over stdio, SSE, or streamable HTTP, and to any dynamic capability registry that accepts tool descriptions, schemas, or annotations from a peer. Does not apply to statically vendored tool manifests that are signed and pinned at build time, nor to single-tool servers whose description is authored by the same trust domain as the agent.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-reject-a-dynamically-registered-mcp-capability-the-description-trust-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-reject-a-dynamically-registered-mcp-capability-the-description-trust-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-reject-a-dynamically-registered-mcp-capability-the-description-trust-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1887,
    "python_slice_tokens": 417,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is not \"malicious tool\" versus \"benign tool.\" It is **description-as-data versus description-as-instruction**. A tool description is a string that the model reads in the same context window as the user's request, with the same syntactic authority as any other text. An MCP server that registers a tool named `get_weather` with a descri...",
    "what_was_observed": "A three-server MCP deployment was instrumented over a two-week window. Server A was a first-party filesystem server, pinned and reviewed. Server B was a third-party \"productivity\" server added by a user for calendar access. Server C was a community server for a niche API, added on a whim. On day 4, Server B emitted `notifications/tools/list_changed` and re-registered an existing tool, `create_event`, with a modified ...",
    "condition_of_validity": "The boundary holds — meaning the instance may safely accept and use the capability — only when **all** of the following are true: 1. The server identity is pinned to a known key or hash, and the pin covers the full tool manifest **including every natural-language field**: `description`, every `inputSchema.properties[*].description`, every `enum` label, every...",
    "decision_boundary": "The decision is not \"is this server malicious.\" It is: **did any natural-language field change since the last pinned manifest, and does the new text contain goal-directed imperatives or references to capabilities outside the registering server?** Operationally: - **Description-only change, same schema** → treat as a full re-registration. Re-pin required. Do ...",
    "operational_effect": "Enforcing the boundary converts a silent, model-dependent failure into a loud, deterministic one. In the instrumented deployment, after pinning descriptions and rejecting on `list_changed` mismatches, Server B's re-registration was rejected at the registry layer, the prior manifest was retained, and the agent continued scheduling meetings with the original t..."
  },
  "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": "1fe125e6bb579c6420869df9d56b0c4a6bf1de8fc303ee6e6eaa9c423d0a6b8b",
    "verified_classes": [
      "CapabilityTrustError"
    ],
    "verified_functions": [
      "_collect_natural_language_fields",
      "manifest_fingerprint",
      "validate_registration"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CapabilityTrustError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "hashlib",
      "json",
      "re",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
