Skip to main content
Glama

cf_list_access_policies

List Cloudflare Access policies for an account or a specific application to review access controls.

Instructions

List Access policies — either account-wide or for a specific app.

Args:
    account_id: account ID.
    app_id: when provided, returns policies attached to that app.
        When omitted, returns all account-level reusable policies.

Calls:
    - GET /accounts/{account_id}/access/apps/{app_id}/policies (app-scoped)
    - GET /accounts/{account_id}/access/policies (account-scoped)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
app_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. Description discloses the two GET endpoints and conditional behavior based on app_id, but lacks details on authentication, rate limits, pagination, or error handling. Adds moderate value beyond schema.

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?

Description is concise and well-structured: purpose in first line, args explained, then underlying API calls. Every sentence is informative with no wasted words.

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?

With 2 parameters, 1 required, and an output schema (existing), the description covers core logic and scope differentiation. It does not mention pagination or sorting, but the output schema likely covers return formats. Fairly complete for a list 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?

Input schema has no descriptions (0% coverage), so description compensates by explaining account_id as 'account ID' and app_id with usage context (when provided vs omitted). Adds significant meaning beyond the schema titles.

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?

Description clearly states the tool lists Access policies, with a specific verb and resource. It distinguishes between account-wide and app-scoped policies, differentiating it from siblings like cf_list_access_apps or cf_get_access_app.

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?

Description explains when to provide app_id vs omit it for account-level policies. It provides clear context but does not explicitly state when not to use this tool or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wojtekkura/cf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server