planka_delete_task
AI agents call planka_delete_task to permanently remove resources in Another Planka MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes tasks, which is an irreversible operation that cannot be undone. This falls into the Destructive category rather than Write (reversible modifications). An AI agent misusing this tool could permanently remove task records from a Planka board, affecting team collaboration and task tracking.
From the tool's definition Tool name 'planka_delete_task' combined with sibling tools including 'mcp_delete_card' and 'mcp_delete_task' in a Planka board management system. The 'delete' prefix indicates irreversible removal of data.
Attacks that exploit this kind of access
planka_delete_task. It is categorised as a Destructive tool in the Another Planka MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Another Planka 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 Another Planka MCP. 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 Another Planka MCP server (roelven/another-planka-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 →