Permanently removes a task from TickTick. You must provide both the task ID and the project ID. This action cannot be undone, and all task data including content, due dates, and tags will be permanently deleted. Use with caution.
AI agents call delete-task to permanently remove resources in Dida — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes task data without recovery options. While not financial in nature, it causes irreversible data loss, making it destructive. The severity is high because an AI agent with incorrect instructions could delete important user tasks unintentionally. The confidence is very high given the explicit language about permanent deletion and inability to undo.
From the tool's definition Tool description explicitly states 'Permanently removes', 'cannot be undone', and 'all task data including content, due dates, and tags will be permanently deleted.' The operation is irreversible deletion.
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 Dida, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-task:
{
"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.
Free to start. No card required.
Permanently removes a task from TickTick. You must provide both the task ID and the project ID. This action cannot be undone, and all task data including content, due dates, and tags will be permanently deleted. Use with caution. It is categorised as a Destructive tool in the Dida MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dida 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 Dida. Nothing to install.
delete-task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete-task is provided by the Dida MCP server (zhongwencool/dida-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dida, 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.
18 Dida tools catalogued and risk-classified — across an index of 43,000+ MCP servers.