deploy_cloudflare_worker · Last Rock MCP: Risk & Policy

WHAT IT DOES

What deploy_cloudflare_worker does on Last Rock MCP

AI agents invoke deploy_cloudflare_worker to trigger actions in Last Rock MCP. 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 IT NEEDS A POLICY

Why deploy_cloudflare_worker needs a policy

Deploying a Cloudflare Worker executes user-provided or AI-specified code in a live production environment. While not immediately destructive (code can be redeployed), it triggers external operations whose effects depend on what code is deployed. This falls squarely in Execute rather than Write because deployment is an operational trigger with side effects beyond simple data modification.

From the tool's definition "Deploy Cloudflare Worker" - the tool deploys code to a production cloud environment (Cloudflare Workers), which executes arbitrary code in a live infrastructure context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_cloudflare_worker Rate-limited

deploy_cloudflare_worker 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_cloudflare_worker": {
      "limits": [
        {
          "counter": "deploy_cloudflare_worker_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Last Rock MCP, so you can run agents against it safely.

FAQ

Questions about deploy_cloudflare_worker

What does the deploy_cloudflare_worker tool do? +

Deploy Cloudflare Worker with state tracking and health checks. DO NOT use ssh_exec(. It is categorised as a Execute tool in the Last Rock MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_cloudflare_worker? +

Register the Last Rock MCP server in PolicyLayer and add a rule for deploy_cloudflare_worker: 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 Last Rock MCP. Nothing to install.

What risk level is deploy_cloudflare_worker? +

deploy_cloudflare_worker is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_cloudflare_worker? +

Yes. Add a rate_limit block to the deploy_cloudflare_worker 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.

How do I block deploy_cloudflare_worker completely? +

Set action: deny in the PolicyLayer policy for deploy_cloudflare_worker. 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.

What MCP server provides deploy_cloudflare_worker? +

deploy_cloudflare_worker is provided by the Last Rock MCP server (itsablabla/lastrock-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.