vulns.co
/
GKData.io MCP and API Buy me a coffee

Model Context Protocol

MCP scope selection: progressive consent and accumulated authority

MCP's official guidance explains how a server's permission requests influence the permissions a general-purpose client asks the user to grant. Broad discovery metadata and permissions accumulated over time can expand that access. The application still needs its own authorization checks even when a token has the requested scopes.

Open the referenceArchitecture GuideReviewed 2026-10-03

How to use this reference

Map operations to permissions, issue focused challenges, support reduced grants and record elevations. Review initial discovery and subsequent consent together; do not assume every authorization request represents only the current operation.

Before reading

  • OAuth scope and consent concepts; client/server authorization responsibilities

Context and limits

  • The guide permits several challenge-breadth strategies. When an initial challenge omits scope, it documents requesting all advertised scopes; it does not universally require the narrowest request.
  • Maintained guidance, not evidence of a specific deployment’s exposure or a verified patch. Publication and edition dates remain unknown; the URL version is preserved separately.

Sources

  1. Security Best Practices: Scope MinimizationModel Context Protocol · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software