get_netflows_data
Retrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId.
This record as markdown: /tools/cloudflare/get-netflows-data.md
What get_netflows_data does on Cloudflare
AI agents call get_netflows_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_netflows_data is rated Low
This tool retrieves network traffic pattern data without modifying, deleting, or executing code. It is a read-only query operation. Severity is medium rather than low because NetFlows data can reveal sensitive network topology, traffic volumes, and patterns that could inform further attacks, though retrieval alone causes no direct damage.
From the tool's definition Tool name 'get_netflows_data' and description 'Retrieve NetFlows traffic data' indicate data retrieval with no modification or deletion. The filtering capability via geoId is a query parameter, not a destructive or side-effecting operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_netflows_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_netflows_data, this is the rule to start with:
get_netflows_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_netflows_data call is checked against it from then on.
Questions about get_netflows_data
Retrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId. 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_netflows_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_netflows_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_netflows_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_netflows_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_netflows_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