dex_create_remote_pcap
Create a remote packet capture (PCAP) for a device. This is a resource intensive and privacy-sensitive operation on a real user device.
This record as markdown: /tools/cloudflare/dex-create-remote-pcap.md
What dex_create_remote_pcap does on Cloudflare
AI agents invoke dex_create_remote_pcap to trigger actions in Cloudflare. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why dex_create_remote_pcap is rated High
This tool triggers an external operation (packet capture) on a real user device. It intercepts network traffic, making it privacy-sensitive and resource-intensive. It does not permanently delete data, but it executes a significant operation on a remote device. The privacy implications and blast radius (capturing all network traffic on a user device) warrant a high severity rating.
From the tool's definition 'Create a remote packet capture (PCAP) for a device. This is a resource intensive and privacy-sensitive operation on a real user device.'
Attacks that exploit this kind of access
The rule that runs dex_create_remote_pcap 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_create_remote_pcap, this is the rule to start with:
dex_create_remote_pcap stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_create_remote_pcap call is checked against it from then on.
Questions about dex_create_remote_pcap
Create a remote packet capture (PCAP) for a device. This is a resource intensive and privacy-sensitive operation on a real user device. It is categorised as a Execute tool in the Cloudflare MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cloudflare MCP server in PolicyLayer and add a rule for dex_create_remote_pcap: 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_create_remote_pcap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dex_create_remote_pcap 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_create_remote_pcap. 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_create_remote_pcap 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.
Across the catalogue