cloudflare-mcp-pro

list_access_rules

Read-only

List IP, ASN, or country access rules for a Cloudflare zone to review block, challenge, or allow actions.

Instructions

List IP/ASN/country access rules (block/challenge/allow) on a zone.

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>"
    },
    "name": "list_access_rules"
  }
}

Input Schema

Name	Required	Description
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`mode`	No	Action to take for matching requests.
`page`	No
`per_page`	No
`fetch_all`	No	When true, follow pagination and return all pages combined (ignores page/per_page).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which convey that the tool is safe and the response structure may vary. The description adds that the rules are IP/ASN/country with block/challenge/allow actions, but does not disclose pagination behavior or any other side effects beyond what annotations imply.

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 a single sentence of 12 words, front-loading the action and scope. Every word is relevant, and there is no redundancy or fluff.

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

Completeness3/5

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

For a list tool with 5 parameters and no output schema, the description is minimal. It does not explain pagination behavior, result format, or how to use the mode filter beyond what's in the schema. The annotations provide some context, but overall the description leaves gaps for a new user.

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

Parameters2/5

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

With schema description coverage at 60%, the parameters page and per_page lack descriptions in both the schema and the tool description. The description does not explain any parameter semantics, leaving these fields ambiguous. While zone_id and mode are described in the schema, the description adds no additional clarity.

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 'List IP/ASN/country access rules (block/challenge/allow) on a zone.' uses a specific verb (List) and clearly identifies the resource (IP/ASN/country access rules) with action types. It distinguishes from sibling tools like list_firewall_rulesets and list_page_rules.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as create_access_rule, delete_access_rule, or list_firewall_rulesets. There is no mention of prerequisites, contexts, or exclusions.

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

Deploy Server