AI agents call cf_workers to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about deployed serverless functions but does not execute, modify, delete, or create them. However, the severity is elevated from 'low' to 'medium' because: (1) it exposes inventory of production code deployments which could inform further attacks, and (2) it operates within a credential proxy system ('one Bearer token, all your services'), meaning compromise of the Access server would…
From the tool's definition Tool description: 'List all Cloudflare Workers scripts deployed in an account, including their names and last-modified timestamps.' The verb 'List' and explicit purpose to 'audit' indicate retrieval of metadata without modification or execution.
Attacks that exploit this kind of access
List all Cloudflare Workers scripts deployed in an account, including their names and last-modified timestamps. Use this to audit deployed serverless functions. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for cf_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 Access. Nothing to install.
cf_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 cf_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 cf_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.
cf_workers is provided by the Access MCP server (scottpedia0/access). 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 →