AI agents call ticktick_delete_task_template 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.
The tool performs a deletion operation ('Remove template'), which falls under the Destructive category as it irreversibly removes data. While the blast radius is limited to templates rather than critical task data, deletion operations cannot be undone and warrant high severity. Confidence is high due to clear deletion semantics in the name and description.
From the tool's definition Tool name 'ticktick_delete_task_template' and description 'Remove template' indicate deletion of a template resource, which is irreversible.
Documented attack patterns abuse exactly the kind of access ticktick_delete_task_template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ticktick_delete_task_template:
{
"version": "1",
"default": "deny",
"hide": [
"ticktick_delete_task_template"
]
} ticktick_delete_task_template 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.
Remove template. 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_delete_task_template: 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_delete_task_template 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_delete_task_template 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_delete_task_template. 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_delete_task_template is provided by the TickTick MCP Server MCP server (liadgez/ticktick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Server, 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.
114 TickTick MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.