reg_delete

Delete registry key/value. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xyg3n-claude-c2/reg-delete.md

WHAT IT DOES

What reg_delete does on Claude C2

AI agents call reg_delete to permanently remove resources in Claude C2, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why reg_delete is rated Critical

Registry modifications are system-critical and persistent; deleting registry keys can disable security features, break system functionality, or cause data loss. This is irreversible and represents the highest-risk category. The context of sibling tools (amsi_bypass, defender_exclude, bypassuac) suggests this is part of a system manipulation toolkit with potential for malicious misuse.

From the tool's definition Tool name 'reg_delete' and description 'Delete registry key/value' explicitly indicates irreversible deletion of Windows registry entries, which cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reg_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reg_delete, this is the rule to start with:

reg_delete Hidden

reg_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every reg_delete call is checked against it from then on.

FAQ

Questions about reg_delete

What does the reg_delete tool do? +

Delete registry key/value. Auto-selects client. It is categorised as a Destructive tool in the Claude C2 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 reg_delete? +

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

What risk level is reg_delete? +

reg_delete 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 reg_delete? +

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

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

reg_delete is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →