Permanently removes multiple tasks from TickTick in a single operation. This batch operation is more efficient than deleting tasks individually. You must provide an array of tasks, where each task must include both the task ID and project ID. This action cannot be undone, and all task data will b...
AI agents call batch-delete-tasks 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 multiple task records in a batch operation with explicit warnings that the action cannot be undone. This is irreversible data loss, placing it firmly in the Destructive category. The batch nature increases the blast radius—a misdirected call could delete hundreds of tasks at once.
From the tool's definition "Permanently removes multiple tasks", "This action cannot be undone, and all task data will be permanently deleted."
Documented attack patterns abuse exactly the kind of access batch-delete-tasks 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 batch-delete-tasks:
{
"version": "1",
"default": "deny",
"hide": [
"batch-delete-tasks"
]
}batch-delete-tasks 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 multiple tasks from TickTick in a single operation. This batch operation is more efficient than deleting tasks individually. You must provide an array of tasks, where each task must include both the task ID and project ID. This action cannot be undone, and all task data 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 batch-delete-tasks: 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.
batch-delete-tasks 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 batch-delete-tasks 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 batch-delete-tasks. 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.
batch-delete-tasks 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.