{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-oauth-2-1-resource-indicator-scoping-has-silently-collapsed-to-token-wide-consent-in-mcp-tool-invocation",
  "title": "What structural signals indicate OAuth 2.1 resource indicator scoping has silently collapsed to token-wide consent in MCP tool invocation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to MCP (Model Context Protocol) servers acting as OAuth 2.1 resource servers that accept `resource` indicators (RFC 8707) and issue consent per resource, where a single authorization server fronts multiple MCP servers or multiple tool surfaces. Does not apply to single-resource deployments where the authorization server and resource server share one audience, nor to servers using pre-registered static audiences with no dynamic `resource` parameter.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-oauth-2-1-resource-indicator-scoping-has-silently-collapsed-to-token-wide-consent-in-mcp-tool-invocation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-oauth-2-1-resource-indicator-scoping-has-silently-collapsed-to-token-wide-consent-in-mcp-tool-invocation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-oauth-2-1-resource-indicator-scoping-has-silently-collapsed-to-token-wide-consent-in-mcp-tool-invocation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1763,
    "python_slice_tokens": 379,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A resource indicator is a *request-scoped narrowing signal*, not an *identity claim about the client*. OAuth 2.1 requires that when a client presents `resource=https://mcp.example.com/tenant-a`, the authorization server must bind the resulting access token's audience to that exact resource and refuse to honor it elsewhere. The non-obvious boundary failure is...",
    "what_was_observed": "In a three-tenant MCP deployment, tenant A's agent requested `resource=https://mcp.example.com/tenant-a` and was granted `tools:invoke` plus `tools:list`. The issued token carried `aud: https://mcp.example.com/tenant-a` and `scope: tools:invoke tools:list`. Every hop validated. The collapse manifested as follows: 1. The authorization server's consent screen rendered the union of scopes registered to the *client*, not...",
    "condition_of_validity": "The collapse is valid to assert only when all four of the following hold simultaneously: - The authorization server accepts dynamic `resource` indicators from unregistered or multi-tenant clients. - The client registration is shared across more than one resource indicator (i.e., the client is not re-registered per resource). - At least one downstream hop (to...",
    "decision_boundary": "Do not treat a passing `aud` check as evidence that resource-indicator scoping is intact. The decision boundary is: - **Assert exact-string audience equality**, not prefix or normalized equality. `aud == configured_resource` must be a byte comparison after a single canonicalization (lowercase scheme+host, no trailing slash), and any divergence must *reject*,...",
    "operational_effect": "When collapse occurs, the observable signature is a *consent-to-invocation divergence rate*: the fraction of invocations whose resolved tool owner does not match the consent record's resource indicator. In a healthy deployment this rate is exactly zero and any non-zero value is an incident. In a collapsed deployment the rate is non-zero but *low* — typically..."
  },
  "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": "fb0e1a7e3ef9ae8060f156f2e08669bf2cb47fa79868d6393360cbe10cdc180d",
    "verified_classes": [
      "ResourceScopeCollapseError",
      "ConsentRecord",
      "InvocationContext"
    ],
    "verified_functions": [
      "_canonical",
      "assert_grant_bound_to_resource"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "ResourceScopeCollapseError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
