cloudflare-mcp-pro

delete_worker_secret

DestructiveIdempotent

Delete a secret binding from a Cloudflare Worker script. Requires human approval to execute, otherwise returns a preview of the change.

Instructions

Delete a secret binding from a Worker script. Requires confirm:true (human-approval gate); without it returns a preview only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script_name": "<script_name>",
      "name": "<name>"
    },
    "name": "delete_worker_secret"
  }
}

Input Schema

Name	Required	Description
`account_id`	No	Cloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.
`script_name`	Yes	The Worker script name.
`name`	Yes	Secret binding name to delete.
`confirm`	No	Human-approval gate: must be true to actually perform this mutating operation. Omit or set false to get a non-executing preview of what would happen (with secrets redacted). A human should approve before this is set to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds behavior beyond annotations by specifying the confirm gate and preview-only mode when confirm is not true. Annotations already indicate destructive and mutating behavior, so the description supplements this with operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, no wasted words. Concisely captures essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema coverage and no output schema, the description covers the core behavior and the crucial confirm gate. It could optionally describe the preview return format, but is sufficient for a simple delete operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline. The description adds meaning to the confirm parameter by explaining its role as a human-approval gate and its effect on preview vs. execution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it deletes a secret binding from a Worker script, which is a specific verb and resource. It distinguishes from sibling delete tools by focusing on worker secrets, but does not explicitly contrast with put_worker_secret.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the critical human-approval gate (confirm:true) and preview behavior, providing clear guidance on how to use the tool. It does not mention when not to use it or alternatives like put_worker_secret.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server