move_card
Move a card to a different list, potentially on a different board
This record as markdown: /tools/io-github-delorenj-mcp-server-trello/move-card.md
What move_card does on Trello
AI agents use move_card to create or update resources in Trello, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello environment.
Why move_card is rated Medium
This tool modifies card metadata (its list/board location) but does not delete, destroy, or create new cards—the operation is reversible by moving the card back. It does not execute arbitrary code, query data without side effects, or involve financial transactions.
From the tool's definition Tool name 'move_card' and description 'Move a card to a different list, potentially on a different board' indicate modification of card state/position.
Attacks that exploit this kind of access
The rule that runs move_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trello, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_card, this is the rule to start with:
move_card stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trello, apply this rule, and every move_card call is checked against it from then on.
Questions about move_card
Move a card to a different list, potentially on a different board. It is categorised as a Write tool in the Trello MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello MCP server in PolicyLayer and add a rule for 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 Trello. Nothing to install.
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 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 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.
move_card is provided by the Trello MCP server (@delorenj/mcp-server-trello). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trello, and thousands of servers like it.
This server
Across the catalogue