archive_list
Send a list to the archive on a specific board
This record as markdown: /tools/io-github-delorenj-mcp-server-trello/archive-list.md
What archive_list does on Trello
AI agents call archive_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.
Why archive_list is rated Critical
Archiving a list in Trello hides it and all its cards from the board. While Trello does allow unarchiving, the operation is not immediately reversible in a standard workflow and has a broad blast radius (all cards in the list are affected). This is closer to a destructive action than a simple write, as it removes content from active use in bulk.
From the tool's definition "Send a list to the archive" — archiving a list removes it from active view and is typically difficult or cumbersome to reverse, affecting all cards within the list.
Attacks that exploit this kind of access
The rule that runs archive_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 archive_list, this is the rule to start with:
archive_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 archive_list call is checked against it from then on.
Questions about archive_list
Send a list to the archive on a specific board. 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.
Register the Trello MCP server in PolicyLayer and add a rule for archive_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.
archive_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 archive_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 archive_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.
archive_list 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.
Across the catalogue