Permanently remove a task. Confirm the user really wants it gone. The server returns the last-known snapshot (summary + detail) for audit purposes.
AI agents call delete_task to permanently remove resources in Schedule Task MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Permanently deleting a scheduled task cannot be reversed and destroys existing configuration/state. While the impact is scoped to task management (not system-wide), the irreversible nature and potential for disruption if an AI agent deletes critical automation tasks makes this Destructive rather than Write.
From the tool's definition Tool name is 'delete_task' and description states 'Permanently remove a task' with language indicating irreversible deletion ('really wants it gone'). The audit snapshot return does not undo the deletion.
Attacks that exploit this kind of access
Permanently remove a task. Confirm the user really wants it gone. The server returns the last-known snapshot (summary + detail) for audit purposes. It is categorised as a Destructive tool in the Schedule Task MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Schedule Task 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 Schedule Task MCP. 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 Schedule Task MCP server (liao1fan/schedule-task-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 →