cloudflare-mcp-pro

create_page_rule

Create a Cloudflare page rule by specifying a URL pattern and actions. Requires confirm:true to apply; omit for a non-executing preview.

Instructions

Create a page rule (URL pattern + actions like cache_level, forwarding_url). Requires confirm:true (human-approval gate); without it returns a preview only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zone_id": "<zone_id>",
      "url_pattern": "<url_pattern>",
      "actions": "<actions>"
    },
    "name": "create_page_rule"
  }
}

Input Schema

Name	Required	Description
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`url_pattern`	Yes	URL match pattern, e.g. example.com/images/.
`actions`	Yes	List of actions to apply when the pattern matches.
`status`	No	Rule status. Default 'active'.
`priority`	No	Rule priority (higher runs first).
`confirm`	No	Human-approval gate: must be true to actually perform this mutating operation. Omit or set false to get a non-executing preview of what would happen (with secrets redacted). A human should approve before this is set to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false (mutating) and destructiveHint=false. The description adds critical behavioral context: the confirm parameter gates execution, and without it the tool only returns a preview. This goes beyond the annotations and clarifies the mutation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences that front-load the main purpose and immediately highlight the critical confirm gate. Every word is necessary; no fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's core behavior and the confirm parameter's effect, including the preview behavior. However, it does not specify return values when confirm:true (presumably the created rule details), which is a minor gap given no output schema. Overall adequate for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with thorough descriptions. The description summarizes key parameters (URL pattern, actions) and adds extra context for the confirm parameter (preview behavior). This adds value beyond the schema, justifying a score above the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'page rule', specifying the key components (URL pattern and actions). It distinguishes this tool from siblings like create_dns_record or create_zone, as page rule creation is unique.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions the confirm parameter as a human-approval gate, guiding when to use it for actual creation vs. preview. However, it does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives, nor does it mention prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server