Skip to main content
Glama
Sign In
mcp-cloudflare-crunchtools

mcp-cloudflare-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Access Policies Tool

list_access_policies_tool
Read-only

List policies on a Cloudflare Access application to review who can reach it. Provide the zone ID and app ID to retrieve all associated access policies.

Instructions

List the policies on an Access application.

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

Input Schema

NameRequiredDescriptionDefault
app_idYesApplication ID (UUID)
zone_idYesZone ID (32-character hex string)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

B3.1/5.0
Behavior2/5

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

The readOnlyHint annotation already declares this is a safe read, and the description adds nothing further - no pagination behavior, no result limits, no note about whether policies are returned in any order. With annotations present the bar is lower, but the description contributes no additional behavioral context.

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?

One short, front-loaded sentence with zero filler; the verb and resource lead the sentence. Nothing is wasted or buried.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, for a list operation there is no mention of pagination, ordering, or result-size expectations, leaving those gaps unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so both zone_id and app_id are already documented (hex string, UUID) in the schema. The description adds no syntax or filtering meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb ('List') and resource ('policies on an Access application'), so an agent can tell it retrieves policies rather than creating or deleting them. It does not name the sibling it relates to (e.g. list_access_apps_tool) or clarify scope, so it stops short of full sibling differentiation.

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?

There is no when-to-use guidance, no mention of prerequisites, and no indication of when to pick this over create_access_policy_tool or delete_access_policy_tool. The agent must infer usage entirely from the name and verb.

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

Deploy Server

Other Tools