copy_checklist
Copy a checklist (with all its items) from one card to another. Works across different boards.
This record as markdown: /tools/io-github-delorenj-mcp-server-trello/copy-checklist.md
What copy_checklist does on Trello
AI agents use copy_checklist 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 copy_checklist is rated Medium
The tool creates new checklist items on a destination card, which is a reversible modification (the copied checklist can be deleted). It does not delete, execute code, move money, or have irreversible effects. While it modifies data, the operation is reversible and scoped to checklist duplication across cards.
From the tool's definition copy_checklist copies data from one card to another, creating new checklist items on the destination card. This is a create/modify operation that results in new data on the target card.
Attacks that exploit this kind of access
The rule that runs copy_checklist 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 copy_checklist, this is the rule to start with:
copy_checklist 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 copy_checklist call is checked against it from then on.
Questions about copy_checklist
Copy a checklist (with all its items) from one card to another. Works across different boards. 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 copy_checklist: 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.
copy_checklist 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 copy_checklist 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 copy_checklist. 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.
copy_checklist 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