TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER
Permanently removes a specific sticker (identified by idSticker) from a Trello card (identified by idCard).
This record as markdown: /tools/trello/trello-delete-cards-stickers-by-id-card-by-id-sticker.md
What TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER does on Trello
AI agents call TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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 |
|---|---|---|---|
idCard | string | — | ID or short link of the card. |
idSticker | string | — | ID of the sticker to remove. |
Parameters from the server's own tool schema.
Why TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER is rated Critical
This tool irreversibly deletes sticker data from a card. While the blast radius is limited (stickers are metadata/cosmetic elements, not core card data), the operation cannot be undone through normal tool restoration. It qualifies as Destructive rather than Write because the action is explicitly permanent and cannot be reversed by the tool itself.
From the tool's definition Tool description states 'Permanently removes' a sticker from a Trello card. The verb 'removes' combined with 'permanently' indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER, this is the rule to start with:
TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER call is checked against it from then on.
Questions about TRELLO_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER
Permanently removes a specific sticker (identified by idSticker) from a Trello card (identified by idCard). 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER accepts 2 parameters: idCard, idSticker. 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER: 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER. 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_DELETE_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER 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