delete_release

THE RISK

Critical Risk

Why delete_release needs a policy

The tool explicitly performs deletion ('delete_release'), which is categorized as Destructive because it removes data permanently. While the blast radius depends on the importance of the release being deleted, the action itself is irreversible.

From the tool's definition 'Delete a release' irreversibly removes a release object from version control or release management systems. This cannot be undone without recovering from backups or re-creating the release manually.

Documented attack patterns abuse exactly the kind of access delete_release gives an agent:

POLICY

How to control delete_release

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_release:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_release"
  ]
}

delete_release disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Claude TypeScript MCP Servers — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude TypeScript MCP Servers tools

Destructive delete_file Delete a file. This operation cannot be undone. Only works within allowed directories. Execute puppeteer_clear_input Clear an input field Execute batch_operations Execute multiple file operations efficiently. Supports transactional mode (rollback on err Execute puppeteer_emulate_device Emulate a specific device Execute puppeteer_evaluate Execute JavaScript in the browser console Execute puppeteer_evaluate_in_frame Execute JavaScript in a specific frame Execute puppeteer_navigate Navigate to a URL Execute puppeteer_wait_for_function Wait for a JavaScript function to return true

All 84 Claude TypeScript MCP Servers tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Claude TypeScript MCP Servers → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_release

What does the delete_release tool do? +

Delete a release. It is categorised as a Destructive tool in the Claude TypeScript MCP Servers MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_release? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for delete_release: 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 Claude TypeScript MCP Servers. Nothing to install.

What risk level is delete_release? +

delete_release is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_release? +

Yes. Add a rate_limit block to the delete_release 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 delete_release completely? +

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

delete_release is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →