planka_remove_card_label
AI agents call planka_remove_card_label 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.
Removing a label from a card is likely irreversible or at least a destructive action (deleting an association). While it may be possible to re-add the label, removal operations are typically classified as Destructive. The sibling tool 'mcp_remove_card_label' further confirms this pattern. Severity is medium since it affects only a label association on a card, not the card or project itself.
From the tool's definition Tool name 'planka_remove_card_label' and sibling tool 'mcp_remove_card_label' suggest removal of a label from a card. The description is empty, so confidence is reduced.
Attacks that exploit this kind of access
planka_remove_card_label. 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_remove_card_label: 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_remove_card_label 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_remove_card_label 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_remove_card_label. 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_remove_card_label 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 →