trello_create_card
AI agents use trello_create_card to create or update resources in Mtl Trello — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mtl Trello environment.
Creating a card is a reversible write operation—it adds data to the board without deleting or permanently modifying existing data. The severity is medium because uncontrolled card creation could clutter boards or spam team members, but the action remains fully reversible through deletion. The empty description slightly lowers confidence, but the tool name is unambiguous.
From the tool's definition Tool name 'trello_create_card' directly indicates creation of a new card on a Trello board. While no description is provided, the name and context (server manages Trello boards, lists, cards, labels, and members) make the intent clear.
Attacks that exploit this kind of access
trello_create_card. It is categorised as a Write tool in the Mtl Trello MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mtl Trello 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 Mtl Trello. 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 Mtl Trello MCP server (musictechlab/mtl-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 →