get_outages_by_location

Get outage counts aggregated by location. Useful for identifying which countries have the most Internet outages.

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/get-outages-by-location.md

What get_outages_by_location does on Cloudflare

AI agents call get_outages_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_outages_by_location is rated Low

This tool performs a read-only operation that queries and aggregates outage data by geographic location. It has no side effects, does not execute code or commands, and does not modify or delete any data. The low severity reflects minimal blast radius if misused—an agent could only retrieve publicly available or authorized outage statistics, which poses no destructive or operational risk.

From the tool's definition Tool name 'get_outages_by_location' and description 'Get outage counts aggregated by location' indicate a query/retrieval operation.

Questions about get_outages_by_location

What does the get_outages_by_location tool do? +

Get outage counts aggregated by location. Useful for identifying which countries have the most Internet outages. 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 get_outages_by_location? +

Register the Cloudflare MCP server in PolicyLayer and add a rule for get_outages_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.

What risk level is get_outages_by_location? +

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

Can I rate-limit get_outages_by_location? +

Yes. Add a rate_limit block to the get_outages_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.

How do I block get_outages_by_location completely? +

Set action: deny in the PolicyLayer policy for get_outages_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.

What MCP server provides get_outages_by_location? +

get_outages_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cloudflare's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.