Cloudflare's MCP server can now ask for more access as it goes
The API MCP server lets you connect with minimal scopes and grants extras on demand, instead of approving every permission an agent might ever need up front.
Cloudflare’s API MCP server added step-up authorization on 19 October. Until now, connecting an agent to mcp.cloudflare.com/mcp meant granting every scope it might touch during the session in one go. You can now choose Minimal on the consent page instead, and the server asks for more only when a tool call actually needs it.
When an agent hits a tool that needs a scope you haven’t granted, the server returns an insufficient_scope challenge naming exactly which one. Your MCP client then prompts you to approve it, and any scopes you already granted stay in place. Cloudflare says this works in any MCP client that supports step-up authorization.
Why it matters: granting broad access up front because an agent “might” need it later is how over-permissioned tokens pile up. Starting minimal and approving scopes as they come up means you only ever grant what a given task actually used, and you can see each expansion as it happens rather than signing off on all of them blind.
The caveat: this only helps if your MCP client actually supports step-up authorization and surfaces the challenge to you. A client that silently auto-approves defeats the point.