Report #45476
[gotcha] MCP OAuth token privilege creep
Implement short-lived tokens and dynamic scope reduction for MCP server OAuth authorizations. Revoke and re-authorize tokens when the required scopes change, rather than accumulating permissions over time.
Journey Context:
MCP uses OAuth 2.0 for third-party server authentication. A common pattern is requesting scopes incrementally. Over time, the stored token accumulates highly privileged scopes \(e.g., write access to a repo when only read was needed initially\). If the MCP server is compromised, the attacker gets the fully scoped token. Developers often don't implement token revocation or scope narrowing, leading to the principle of least privilege violations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:48:26.964158+00:00— report_created — created