TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST
Moves all cards from a Trello list to a *different* board; this action is irreversible, moves (not copies) cards, and empties the source list without deleting it.
This record as markdown: /tools/trello/trello-add-lists-move-all-cards-by-id-list.md
What TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST does on Trello
AI agents call TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST to permanently remove resources in Trello, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
idList | string | — | The ID of the source Trello list from which all cards will be moved. |
idBoard | string | — | The ID of the destination Trello board to which all cards from the source list will be moved. This parameter is required by Trello for this operation. |
Parameters from the server's own tool schema.
Why TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST is rated Critical
Although cards themselves are not deleted, moving all cards away from a list is an irreversible operation that fundamentally transforms the source list and disrupts the original board structure. The data cannot be easily recovered or undone through normal UI operations.
From the tool's definition Tool description states 'this action is irreversible' and 'moves (not copies) cards' from one board to another, effectively removing them from their original context. The operation empties the source list without recovery options.
Attacks that exploit this kind of access
The rule that runs TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST 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 TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST, this is the rule to start with:
TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Trello, apply this rule, and every TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST call is checked against it from then on.
Questions about TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST
Moves all cards from a Trello list to a *different* board; this action is irreversible, moves (not copies) cards, and empties the source list without deleting it. It is categorised as a Destructive tool in the Trello MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST accepts 2 parameters: idList, idBoard. The full parameter table on this page comes from the server's own tool schema.
Register the Trello MCP server in PolicyLayer and add a rule for TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST: 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.
TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST 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_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST. 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_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST is provided by the Trello MCP server (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.
Across the catalogue