dex_fleet_status_live
Retrieve details about the real-time status of the fleet of devices broken down by dimension (mode, status, colo, platform, version)
This record as markdown: /tools/cloudflare/dex-fleet-status-live.md
What dex_fleet_status_live does on Cloudflare
AI agents call dex_fleet_status_live 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 dex_fleet_status_live is rated Low
This tool queries fleet device status information and returns aggregated metrics broken down by various dimensions (mode, status, colo, platform, version). It has no side effects, does not execute code, does not modify data, and does not trigger external operations. The blast radius of misuse is minimal—an agent could only access status visibility, which is typically non-sensitive operational metadata.
From the tool's definition Tool name and description explicitly indicate 'Retrieve details about the real-time status' with no modification, deletion, or execution capabilities. The verb 'Retrieve' and the focus on status querying confirm read-only semantics.
Attacks that exploit this kind of access
The rule that runs dex_fleet_status_live 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 dex_fleet_status_live, this is the rule to start with:
dex_fleet_status_live 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 dex_fleet_status_live call is checked against it from then on.
Questions about dex_fleet_status_live
Retrieve details about the real-time status of the fleet of devices broken down by dimension (mode, status, colo, platform, version). 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 dex_fleet_status_live: 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.
dex_fleet_status_live 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 dex_fleet_status_live 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 dex_fleet_status_live. 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.
dex_fleet_status_live 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