Delete a task permanently. ⚠ Cannot be undone — confirm with the user before calling. Time entries linked to this task will also be deleted (cascade).
AI agents call delete_task to permanently remove resources in Rhizm MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete_task permanently removes data without possibility of recovery and cascades deletion to related time entries. This is an irreversible operation that cannot be undone, fitting the Destructive category. Severity is high because loss of task data and associated time tracking information has significant user impact, though not financial in nature.
From the tool's definition Tool description states 'Delete a task permanently' and '⚠ Cannot be undone' with explicit warning that 'Time entries linked to this task will also be deleted (cascade)'. This is irreversible data deletion.
Attacks that exploit this kind of access
Delete a task permanently. ⚠ Cannot be undone — confirm with the user before calling. Time entries linked to this task will also be deleted (cascade). It is categorised as a Destructive tool in the Rhizm MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rhizm MCP Server 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 Rhizm MCP Server. 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 Rhizm MCP Server MCP server (rhizmapp/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 →