Delete multiple tasks in a single request.
AI agents call ticktick_batch_delete_tasks to permanently remove resources in TickTick MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (tasks) from the user's TickTick account. Deletion cannot be undone, and the batch capability means a single misuse could destroy many tasks at once, causing significant data loss. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'
From the tool's definition Tool name explicitly states 'delete' and description says 'Delete multiple tasks in a single request.' The batch operation amplifies the destructive impact.
Attacks that exploit this kind of access
Delete multiple tasks in a single request. It is categorised as a Destructive tool in the TickTick MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_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 TickTick MCP Server. Nothing to install.
ticktick_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 ticktick_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 ticktick_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.
ticktick_batch_delete_tasks is provided by the TickTick MCP Server MCP server (mostafasuliman/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →