Critical Risk →

delete_task

Delete a task from a request.

How to control delete_task ↓

What delete_task does on MCP TaskManager

AI agents call delete_task to permanently remove resources in MCP TaskManager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_task needs a policy

This tool permanently removes a task from the system. Deletion is irreversible and cannot be undone through normal operations. While the blast radius is contained to individual task records (not system-wide destruction), the irreversible nature of deletion and potential impact on task workflows, planning, and accountability justifies the Destructive category over Write.

From the tool's definition Tool name is 'delete_task' and description states 'Delete a task from a request.' The verb 'delete' explicitly indicates irreversible removal of data.

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

How to control delete_task

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_task"
  ]
}

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

  1. Create a free account and register MCP TaskManager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_task

What does the delete_task tool do? +

Delete a task from a request. It is categorised as a Destructive tool in the MCP TaskManager 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_task? +

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

What risk level is delete_task? +

delete_task 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_task? +

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

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

delete_task is provided by the MCP TaskManager MCP server (rudra-ravi/mcp-taskmanager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP TaskManager tool call.

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

Free to start. No card required.

10 MCP TaskManager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.