Critical Risk →

delete_task

Delete a specific task from a request. Only uncompleted tasks can be deleted.\n\n

How to control delete_task ↓

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

Critical Risk

An AI agent that decides to call delete_task doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from TaskFlow MCP is gone — there is no undo for destructive operations.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and TaskFlow MCP, 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 TaskFlow MCP — 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.

Go deeper

What does the delete_task tool do? +

Delete a specific task from a request. Only uncompleted tasks can be deleted.\n\n. It is categorised as a Destructive tool in the TaskFlow MCP 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 TaskFlow 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 TaskFlow MCP. 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 TaskFlow MCP server (pinkpixel-dev/taskflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TaskFlow MCP tool call.

Deterministic rules across all 23 TaskFlow MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

23 TaskFlow MCP tools catalogued and risk-classified — across an index of 42,500+ 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.