archive_card
Archive (close) a card. Trello has no hard delete via this server.
This record as markdown: /tools/artemnikov-trello-mcp/archive-card.md
What archive_card does on Trello
AI agents use archive_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 archive_card is rated Medium
Archiving a card modifies its state reversibly (it can be restored), making this a Write operation rather than Destructive. The severity is medium because archiving removes a card from active view and workflow, potentially disrupting team productivity if done without authorization, but the action is not irreversible. Confidence is high due to the clear, explicit description that confirms reversibility.
From the tool's definition Tool named 'archive_card' with description 'Archive (close) a card.' The description explicitly states 'Trello has no hard delete via this server,' confirming the action is reversible—archived cards can be unarchived in Trello.
Attacks that exploit this kind of access
The rule that runs archive_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 archive_card, this is the rule to start with:
archive_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 archive_card call is checked against it from then on.
Questions about archive_card
Archive (close) a card. Trello has no hard delete via this server. 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 archive_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.
archive_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 archive_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 archive_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.
archive_card is provided by the Trello MCP server (artemnikov/trello-mcp). 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