Delete a task by its unique ID.
AI agents call delete_task to permanently remove resources in Omniplan — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a task from OmniPlan, which cannot be undone and could impact project timelines, resource allocation, and team coordination. In a project management context, deleting tasks is a destructive action that cannot be reversed. The high severity reflects that an AI agent misusing this could cause significant disruption by removing critical project work items.
From the tool's definition Tool name is 'delete_task' and description states 'Delete a task by its unique ID.' The verb 'delete' combined with the irreversible removal of a task from a project management system indicates destructive functionality.
Attacks that exploit this kind of access
Delete a task by its unique ID. It is categorised as a Destructive tool in the Omniplan MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Omniplan 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 Omniplan. 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 Omniplan MCP server (johntrandall/omniplan-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 →