This record as markdown: /tools/io-github-kivanccakmak-yaver/cf-workers.md
What cf_workers does on Yaver
AI agents call cf_workers to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why cf_workers is rated Low
The verb 'List' combined with 'deployments' shows this tool only queries and retrieves data about Cloudflare Workers. There are no side effects, state changes, code execution, or destructive operations. It is a straightforward information retrieval operation, fitting the Read category.
From the tool's definition Tool name 'cf_workers' and description 'List Cloudflare Worker deployments' indicate a read-only query operation that retrieves information about existing deployments without modifying or deleting anything.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs cf_workers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cf_workers, this is the rule to start with:
cf_workers 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 Yaver, apply this rule, and every cf_workers call is checked against it from then on.
Questions about cf_workers
List Cloudflare Worker deployments. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
cf_workers accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue