task_delete

DESTRUCTIVE: delete a scheduled task immediately (schtasks /delete /f). No confirmation prompt.

SERVERMcp Hands SOURCEhuocai250/mcp-hands

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/mcp-hands/task-delete.md

WHAT IT DOES

What task_delete does on Mcp Hands

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

RISK

Why task_delete is rated Critical

An AI agent that decides to call task_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Hands is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs task_delete safely

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

task_delete Hidden

task_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": [
    "task_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about task_delete

What does the task_delete tool do? +

DESTRUCTIVE: delete a scheduled task immediately (schtasks /delete /f). No confirmation prompt. It is categorised as a Destructive tool in the Mcp Hands 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 task_delete? +

Register the Mcp Hands MCP server in PolicyLayer and add a rule for task_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 Mcp Hands. Nothing to install.

What risk level is task_delete? +

task_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 task_delete? +

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

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

task_delete is provided by the Mcp Hands MCP server (huocai250/mcp-hands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Hands, and thousands of servers like it.

This server

All 378 Mcp Hands 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 →