Permanently delete a project and ALL its tasks. ⚠️ IRREVERSIBLE.
AI agents call delete_project to permanently remove resources in Tick — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys data (project and cascading task deletion) with no undo capability. It represents the most severe category of misuse risk—an AI agent given this tool could erase an entire project structure, causing permanent data loss. The irreversible nature and blast radius of deleting an entire project plus all associated tasks warrant critical severity.
From the tool's definition Tool description explicitly states 'Permanently delete a project and ALL its tasks. ⚠️ IRREVERSIBLE.' The combination of 'permanently', 'ALL its tasks', and the irreversibility warning indicates data deletion with no recovery path.
Attacks that exploit this kind of access
Permanently delete a project and ALL its tasks. ⚠️ IRREVERSIBLE. It is categorised as a Destructive tool in the Tick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tick 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 Tick. 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 Tick MCP server (kpihx/tick-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 →