create-card
AI agents use create-card to create or update resources in Trello MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello MCP Server environment.
Creating a card in Trello is a reversible write operation that modifies workspace state by adding new data. It is not destructive (data is not deleted or overwritten irreversibly), not financial, and not code execution. The severity is medium because an AI agent creating many cards could spam or clutter a board, but the action is reversible through archival or deletion.
From the tool's definition Tool name 'create-card' and server description explicitly states 'creating' cards are supported operations. Server description confirms this tool enables 'creating, moving, archiving cards' as core functionality.
Attacks that exploit this kind of access
create-card. It is categorised as a Write tool in the Trello MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello MCP Server MCP server in PolicyLayer and add a rule for 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 Trello MCP Server. Nothing to install.
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 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 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.
create-card is provided by the Trello MCP Server MCP server (praveencs87/trello-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 →