Takeaway
On October 19, 2026, Cloudflare announced step-up authorization for its API MCP server. Teams can choose Minimal when connecting and approve additional permissions when a task needs them. The feature is available now, but only in MCP clients that support this mechanism.
Who benefits
Business owners whose employees or contractors use an AI agent to work with Cloudflare. MCP is the connection between the assistant and the service. According to Cloudflare’s documentation, this connection can read configurations and make changes. Understanding the permissions granted to the agent therefore matters.
What changes
When a tool request lacks a required permission, the server returns an insufficient_scope challenge identifying it, and a compatible client asks for approval. Previously granted permissions remain. The MCP specification describes this as an incremental expansion of authorized scopes.
This is not a promise to ask a person before every subsequent action, nor automatic revocation of earlier permissions. Once an agent has the necessary permission, the step-up mechanism itself does not create a new approval for every use.
What to ask the person responsible
Nadali’s editorial recommendation is to ask your contractor three questions before a new connection or a review of an existing one.
- Does our MCP client support step-up authorization? Supporting MCP alone does not establish compatibility.
- Which initial permissions does this particular task need, and which changes remain outside its scope?
- Who approves expanded access, and who reviews accumulated permissions after the work ends?
Illustrative example: if the job is only to inspect website configuration, a request for permission to change it should first be checked against the agreed task. This is a workflow example, not a test result.
Availability and limits
The announcement concerns the Cloudflare API MCP server, not every AI tool or every way of accessing Cloudflare. Nadali checked public sources but did not test clients or a customer account. The mechanism does not guarantee security or replace an internal change-approval process.
Bottom line: start with access needed for the task, review each expansion and separately review permissions already granted.
Read also: preparing an access review after a role change.
Sources checked on October 22, 2026. Author: Nadali. Prepared with AI.
Cover: an original AI-generated illustration for Nadali, not an interface screenshot or evidence of testing.
