delete_task

THE RISK

Critical Risk

Why delete_task needs a policy

This tool permanently removes a task from the TickTick system with no undo capability mentioned. Deletion is irreversible and represents data loss. While the blast radius is somewhat contained (single task rather than batch deletion via delete_project), the destructive nature and potential for accidental or malicious removal of user tasks warrants a 'high' severity classification.

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

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

POLICY

How to control delete_task

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

Create a free account and register Ticktick — 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 Ticktick tools

Destructive delete_project Delete a project. Args: project_id: ID of the project Write batch_create_tasks batch_create_tasks Write complete_task Mark a task as complete. Args: project_id: ID of the project task Write create_project Create a new project in TickTick. Args: name: Project name color: Write create_subtask Create a subtask for a parent task within the same project. Args: subtask Write create_task Create a new task in TickTick. Args: title: Task title project_id Write update_task Update an existing task in TickTick. Args: task_id: ID of the task to upd Read get_all_tasks Get all tasks from TickTick. Ignores closed projects.

All 22 Ticktick 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 Ticktick → 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_task

What does the delete_task tool do? +

Delete a task. Args: project_id: ID of the project task_id: ID of the task. It is categorised as a Destructive tool in the Ticktick 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 Ticktick 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 Ticktick. 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 Ticktick MCP server (jacepark12/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ticktick tool call.

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

CHECK YOUR STACK →