List all Cloudflare Workers scripts deployed in an account. e.g., account_id
AI agents call list_workers to retrieve information from Cloudflare Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only lists/queries existing Workers scripts—a read operation with no side effects. While Workers can execute code, merely listing them reveals only metadata about deployed scripts, not their execution. The blast radius is low: the information disclosed is limited to names and basic metadata of the user's own Workers, which does not enable unauthorized actions without additional exploit steps.
From the tool's definition Tool name 'list_workers' and description 'List all Cloudflare Workers scripts deployed in an account' indicate a read-only operation that retrieves and enumerates existing Workers without modification.
Attacks that exploit this kind of access
List all Cloudflare Workers scripts deployed in an account. e.g., account_id. It is categorised as a Read tool in the Cloudflare Control MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare Control MCP server in PolicyLayer and add a rule for list_workers: 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 Control. Nothing to install.
list_workers 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 list_workers 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 list_workers. 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.
list_workers is provided by the Cloudflare Control MCP server (josephtandle/cloudflare-mcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →