cloudflare-mcp-pro

create_access_rule

Create an IP, ASN, or country access rule with actions like block, challenge, or whitelist. Requires confirmation to execute; without it, returns a preview.

Instructions

Create an IP/ASN/country access rule (block, challenge, or whitelist). 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>",
      "mode": "<mode>",
      "target": "<target>",
      "value": "<value>"
    },
    "name": "create_access_rule"
  }
}

Input Schema

Name	Required	Description
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`mode`	Yes	Action to take for matching requests.
`target`	Yes	What the rule matches on.
`value`	Yes	Match value, e.g. '1.2.3.4', '1.2.3.0/24', 'AS13335', or 'US'.
`notes`	No	Optional note describing the rule.
`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.6/5.0

Behavior5/5

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

The description adds significant behavioral context beyond annotations: the confirm gate and preview vs. execution modes. Annotations only provide readOnlyHint=false, destructiveHint=false, etc., but the description details the actual operation 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?

The description is extremely concise: two sentences that efficiently convey purpose and key usage guideline. No superfluous information.

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?

Given the lack of an output schema and the openWorldHint annotation, the description covers the critical behavioral nuance of confirm. It could mention return values or error states, but for a creation tool it is adequately complete.

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 clear parameter descriptions. The description adds extra semantic value for the confirm parameter (human-approval gate, preview vs. execution), enhancing understanding of its role.

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 'IP/ASN/country access rule', and lists specific actions (block, challenge, whitelist). It distinguishes this from sibling create_* tools by specifying 'access rule'.

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

Usage Guidelines4/5

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

The description explicitly states the mandatory confirm:true for execution and the preview behavior without it, providing critical usage context. However, it does not compare to alternatives like update or delete access rules, but the given context is sufficient for the main use case.

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

Deploy Server