Create a new card in a specified list.
AI agents use mcp_create_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.
This tool creates new cards (data records) in a Planka board list, which is a reversible Write operation. It does not execute arbitrary code, delete data, move money, or trigger destructive actions. The severity is medium because uncontrolled card creation could clutter boards or be used for spam, but the impact is limited to board organization and can be reversed through deletion.
From the tool's definition Tool name 'mcp_create_card' and description 'Create a new card in a specified list' explicitly indicates creation of new data in the Planka board system.
Attacks that exploit this kind of access
Create a new card in a specified list. 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_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 Another Planka MCP. Nothing to install.
mcp_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 mcp_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 mcp_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.
mcp_create_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 →