Batch create, update, and/or delete multiple tasks in a single request
AI agents call batch_update_tasks to permanently remove resources in Ticktick — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports deleting multiple tasks in a single operation, which is irreversible. Since it spans Write and Destructive categories, the most severe (Destructive) applies. The batch nature increases the blast radius significantly — an AI agent could delete many tasks at once.
From the tool's definition 'Batch create, update, and/or delete multiple tasks in a single request'
Documented attack patterns abuse exactly the kind of access batch_update_tasks gives an agent:
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 batch_update_tasks:
{
"version": "1",
"default": "deny",
"hide": [
"batch_update_tasks"
]
}batch_update_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.
Batch create, update, and/or delete multiple tasks in a single request. 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.
Register the Ticktick MCP server in PolicyLayer and add a rule for batch_update_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. Nothing to install.
batch_update_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_update_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_update_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_update_tasks is provided by the Ticktick MCP server (@alexarevalo.ai/mcp-server-ticktick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ticktick, 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.
16 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.