list_geolocations

List available geolocations (ADM1 - administrative divisions like states/provinces). Use this to find GeoNames IDs for filtering HTTP and NetFlows data by region.

SERVERCloudflare SOURCEhttps://builds.mcp.cloudflare.com/sse

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/cloudflare/list-geolocations.md

WHAT IT DOES

What list_geolocations does on Cloudflare

AI agents call list_geolocations to retrieve information from Cloudflare without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_geolocations is rated Low

This tool retrieves reference data about geographical locations and administrative divisions for filtering purposes. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only obtain lists of available geolocation identifiers, which is non-sensitive metadata.

From the tool's definition Tool name 'list_geolocations' and description 'List available geolocations' indicate a read operation that retrieves or queries geolocation data.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_geolocations safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_geolocations, this is the rule to start with:

list_geolocations Allowed

list_geolocations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_geolocations": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every list_geolocations call is checked against it from then on.

FAQ

Questions about list_geolocations

What does the list_geolocations tool do? +

List available geolocations (ADM1 - administrative divisions like states/provinces). Use this to find GeoNames IDs for filtering HTTP and NetFlows data by region. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_geolocations? +

Register the Cloudflare MCP server in PolicyLayer and add a rule for list_geolocations: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cloudflare. Nothing to install.

What risk level is list_geolocations? +

list_geolocations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_geolocations? +

Yes. Add a rate_limit block to the list_geolocations rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_geolocations completely? +

Set action: deny in the PolicyLayer policy for list_geolocations. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_geolocations? +

list_geolocations is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cloudflare, and thousands of servers like it.

This server

All 92 Cloudflare tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →