get_origins_data
Retrieve cloud provider (AWS, GCP, Azure, OCI) performance metrics. Supports timeseries, summaries grouped by region/success_rate/percentile, and grouped timeseries.
This record as markdown: /tools/cloudflare/get-origins-data.md
What get_origins_data does on Cloudflare
AI agents call get_origins_data 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_origins_data is rated Low
This tool retrieves performance metrics from cloud providers without creating, modifying, or deleting data. However, severity is elevated to medium rather than low because performance metrics can reveal infrastructure patterns, capacity planning details, and operational insights that could be sensitive information useful to an attacker for reconnaissance or planning attacks against Cloudflare's infrastructure.
From the tool's definition Tool description states 'Retrieve cloud provider...performance metrics' with support for 'timeseries, summaries grouped by region/success_rate/percentile, and grouped timeseries.' The verb 'Retrieve' and the focus on querying metrics indicate data retrieval…
Attacks that exploit this kind of access
The rule that runs get_origins_data 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_origins_data, this is the rule to start with:
get_origins_data 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_origins_data call is checked against it from then on.
Questions about get_origins_data
Retrieve cloud provider (AWS, GCP, Azure, OCI) performance metrics. Supports timeseries, summaries grouped by region/success_rate/percentile, and grouped timeseries. 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_origins_data: 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_origins_data 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_origins_data 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_origins_data. 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_origins_data 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