This record as markdown: /tools/abdwyer-trellomcp/move-card.md
What move_card does on Trello MCP Server
AI agents use move_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.
Why move_card is rated Medium
Moving a card changes its list assignment but is fully reversible—the card can be moved back to its original list without data loss. This qualifies as Write rather than Execute (no arbitrary code runs) or Destructive (the operation is undoable).
From the tool's definition Tool description explicitly states it "Move[s] a Trello card to a different list," which modifies card state (position/list assignment) reversibly. The server description notes "full CRUD operations" and "card movement," confirming this is a write operation.
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 MCP Server, 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 MCP Server, apply this rule, and every move_card call is checked against it from then on.
Questions about move_card
Move a Trello card to a different list. 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 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 MCP Server. 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 MCP server (abdwyer/trellomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trello MCP Server, and thousands of servers like it.
This server
Across the catalogue