Move a Trello card to a different list.
AI agents use trello_move_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.
This tool modifies the state of data (card location) but does not permanently delete or destroy information, nor does it execute arbitrary code or trigger uncontrolled external operations. It is reversible—a card can be moved back. The risk is medium because misuse could disorganize work or move sensitive cards to wrong lists, but the impact is limited in scope and easily remediated.
From the tool's definition The tool description states it will 'Move a Trello card to a different list.' Moving is a reversible modification of card state/position within a Trello board.
Attacks that exploit this kind of access
Move a Trello card to a different list. 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_move_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_move_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_move_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_move_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_move_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 →