Create a new card in a list
AI agents use planka_create_card to create or update resources in Planka MCP Server for Claude — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planka MCP Server for Claude environment.
This tool creates a new card (a reversible, non-destructive data modification) in a Planka kanban board. Card creation is a standard write operation with no side effects beyond adding a record to a list. The action is easily undoable (card can be deleted), and the blast radius from misuse is limited to unwanted cards appearing in a list.
From the tool's definition Tool name 'planka_create_card' and description 'Create a new card in a list' indicate data creation in a project management system.
Attacks that exploit this kind of access
Create a new card in a list. It is categorised as a Write tool in the Planka MCP Server for Claude MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_create_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 Planka MCP Server for Claude. Nothing to install.
planka_create_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_create_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_create_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_create_card is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). 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 →