This record as markdown: /tools/abdwyer-trellomcp/delete-checklist.md
What delete_checklist does on Trello MCP Server
AI agents call delete_checklist to permanently remove resources in Trello MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_checklist is rated Critical
This tool performs an irreversible deletion operation on Trello data. Although the blast radius is moderate (limited to a single checklist rather than an entire board or card), the action cannot be undone programmatically and represents permanent data loss. Destructive category is appropriate as deletion operations take precedence over Write or Execute categories.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a Trello checklist.' The operation removes a checklist irreversibly from a Trello card.
Attacks that exploit this kind of access
The rule that runs delete_checklist 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 delete_checklist, this is the rule to start with:
delete_checklist 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 MCP Server, apply this rule, and every delete_checklist call is checked against it from then on.
Questions about delete_checklist
Delete a Trello checklist. It is categorised as a Destructive tool in the Trello MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trello MCP Server MCP server in PolicyLayer and add a rule for delete_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 MCP Server. Nothing to install.
delete_checklist 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 delete_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 delete_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.
delete_checklist 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.
Across the catalogue