Delete a project. Args: project_id: ID of the project
AI agents call delete_project 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.
Deleting a project is irreversible and will likely remove all associated tasks and data within that project. This is a destructive operation that cannot be undone, fitting the Destructive category. Severity is high because accidentally deleting a project could result in significant loss of organized work and task information. The confidence is high because the intent is explicit and unambiguous.
From the tool's definition Tool name is "delete_project" and description states "Delete a project." The word "delete" indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_project 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 delete_project:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project"
]
} delete_project 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.
Delete a project. Args: project_id: ID of the project. 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 delete_project: 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.
delete_project 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 delete_project 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 delete_project. 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.
delete_project is provided by the Ticktick MCP server (jacepark12/ticktick-mcp). 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.
22 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.