delete_task
Move the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded.
This record as markdown: /tools/402cron/delete-task.md
What delete_task does on 402cron
AI agents call delete_task to permanently remove resources in 402cron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Task id (UUID), as returned by create_task or list_tasks. |
Parameters from the server's own tool schema.
Why delete_task is rated Critical
An AI agent that decides to call delete_task doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 402cron is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402cron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_task, this is the rule to start with:
delete_task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 402cron, apply this rule, and every delete_task call is checked against it from then on.
Questions about delete_task
Move the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded. It is categorised as a Destructive tool in the 402cron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_task accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the 402cron MCP server in PolicyLayer and add a rule for delete_task: 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 402cron. Nothing to install.
delete_task 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_task 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_task. 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_task is provided by the 402cron MCP server (https://402cron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402cron, and thousands of servers like it.
Across the catalogue