Add a label to a card.
AI agents use mcp_add_card_label to create or update resources in Another Planka MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Another Planka MCP environment.
This tool creates or modifies data (adds a label association) in a reversible manner. Labels can be removed or changed, so the operation is not destructive. The blast radius is minimal—incorrect label application affects only card organization/metadata within a single project management board, with no data loss or external system impact.
From the tool's definition Tool name 'mcp_add_card_label' and description 'Add a label to a card' indicate a create/modify operation that adds metadata to an existing card in a Planka board.
Attacks that exploit this kind of access
Add a label to a card. It is categorised as a Write tool in the Another Planka MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Another Planka MCP server in PolicyLayer and add a rule for mcp_add_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.
mcp_add_card_label is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mcp_add_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 mcp_add_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.
mcp_add_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 →