planka_update_card
AI agents use planka_update_card 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.
The tool updates card data in a Planka board, which is a reversible modification operation. This falls under Write category. Severity is medium because card updates in a project management system could affect task status and team coordination, but the operation is not destructive or financial.
From the tool's definition Tool name 'planka_update_card' combined with sibling tools context showing create, delete, and label operations on Planka cards.
Attacks that exploit this kind of access
planka_update_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 planka_update_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_update_card 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 planka_update_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_update_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_update_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 →