Create a new card
AI agents use trello_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 is a write operation—it adds data to Trello boards and lists but is fully reversible (the card can be deleted). The blast radius is medium because a compromised agent could spam cards or clutter boards, but the impact is limited to a single workspace and easily undone. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool creates a new card in Trello, as stated in the description 'Create a new card'. This is a reversible creation operation that modifies data by adding a new entity to a board.
Attacks that exploit this kind of access
Create a new 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 trello_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.
trello_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 trello_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 trello_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.
trello_create_card is provided by the Trello MCP Server MCP server (shameerpc5029/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 →