Delete a project folder.
AI agents call ticktick_delete_folder 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.
Deleting a folder in a task management system irreversibly removes data structures and potentially all contained items. This cannot be undone and matches the Destructive category definition. Severity is high because it can wipe out significant user data (all tasks in a folder), though the blast radius is limited to one folder rather than the entire TickTick account.
From the tool's definition Tool name includes 'delete' and description states 'Delete a project folder' — a folder likely contains multiple tasks/projects and deletion is irreversible.
Attacks that exploit this kind of access
Delete a project folder. 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_folder: 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_folder 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_folder 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_folder. 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_folder 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 →