get_http_data
Retrieve HTTP traffic trends.
This record as markdown: /tools/cloudflare/get-http-data.md
What get_http_data does on Cloudflare
AI agents call get_http_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_http_data is rated Low
This tool retrieves existing HTTP traffic data for analysis purposes. It queries or fetches trends without creating, modifying, deleting, or executing any operations. The read-only nature and informational output (trends) place it squarely in the Read category with low severity.
From the tool's definition Tool name and description: 'Retrieve HTTP traffic trends' indicates data retrieval with no modification capability. The verb 'Retrieve' is a read operation, and traffic trends are analytical summaries without side effects.
Attacks that exploit this kind of access
The rule that runs get_http_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_http_data, this is the rule to start with:
get_http_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_http_data call is checked against it from then on.
Questions about get_http_data
Retrieve HTTP traffic trends. 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_http_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_http_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_http_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_http_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_http_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