Delete a task
AI agents call planka_delete_task to permanently remove resources in Planka MCP Server for Claude — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are inherently destructive because they remove data that cannot be recovered without external backups. In a project management context, deleting a task eliminates work tracking information. This warrants the Destructive category with high severity due to the permanent nature of the action and its potential impact on project records and team collaboration.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a task'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a task. It is categorised as a Destructive tool in the Planka MCP Server for Claude MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_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 Planka MCP Server for Claude. Nothing to install.
planka_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 planka_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 planka_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.
planka_delete_task is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). 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 →