get_traffic_anomalies_by_location
Get traffic anomalies aggregated by location. Shows which countries have the most detected outage signals, automatically detected by Radar.
This record as markdown: /tools/cloudflare/get-traffic-anomalies-by-location.md
What get_traffic_anomalies_by_location does on Cloudflare
AI agents call get_traffic_anomalies_by_location 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.
Why get_traffic_anomalies_by_location is rated Low
This tool retrieves and displays aggregated traffic anomaly data detected by Cloudflare's Radar system. It performs no side effects, creates no resources, executes no code, and does not modify or delete data. The operation is read-only and informational, making it a low-severity Read category tool.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get traffic anomalies aggregated by location' with no mutation, deletion, or execution capabilities. It queries Cloudflare Radar's pre-computed anomaly data.
Attacks that exploit this kind of access
The rule that runs get_traffic_anomalies_by_location 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 get_traffic_anomalies_by_location, this is the rule to start with:
get_traffic_anomalies_by_location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every get_traffic_anomalies_by_location call is checked against it from then on.
Questions about get_traffic_anomalies_by_location
Get traffic anomalies aggregated by location. Shows which countries have the most detected outage signals, automatically detected by Radar. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for get_traffic_anomalies_by_location: 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.
get_traffic_anomalies_by_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_traffic_anomalies_by_location 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.
Set action: deny in the PolicyLayer policy for get_traffic_anomalies_by_location. 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.
get_traffic_anomalies_by_location 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.
More on Cloudflare, and thousands of servers like it.
This server
Across the catalogue