planka_delete_card
AI agents call planka_delete_card 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.
Delete operations are irreversible and permanently remove data from the Planka board. This constitutes a Destructive action with high severity due to the potential loss of important project/card information. Even without a description, the delete operation name leaves no ambiguity. Confidence is high despite empty description because the action is unambiguous from the tool name and context.
From the tool's definition Tool name is 'planka_delete_card' which explicitly performs a delete operation. The sibling tool 'mcp_delete_task' and the presence of other deletion operations confirm this server supports destructive actions on Planka board data.
Attacks that exploit this kind of access
planka_delete_card. 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_card: 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_card 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_card 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_card. 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_card 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 →