TRELLO_DELETE_MEMBER_CUSTOM_STICKER
Deletes a custom sticker from a Trello member's collection; this permanent action is only available for custom stickers within a Trello Workspace on a paid plan.
This record as markdown: /tools/trello/trello-delete-member-custom-sticker.md
What TRELLO_DELETE_MEMBER_CUSTOM_STICKER does on Trello
AI agents call TRELLO_DELETE_MEMBER_CUSTOM_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 |
|---|---|---|---|
idMember | string | — | The ID or username of the Trello member. |
idCustomSticker | string | — | The ID of the custom sticker to be deleted from the member's collection. |
Parameters from the server's own tool schema.
Why TRELLO_DELETE_MEMBER_CUSTOM_STICKER is rated Critical
The tool irreversibly deletes data (a custom sticker) from a member's collection. While the blast radius is limited to sticker assets rather than core business data (cards, boards, lists), the permanent nature of deletion places it in the Destructive category.
From the tool's definition "Deletes a custom sticker from a Trello member's collection; this permanent action" — the tool explicitly describes a permanent deletion that cannot be undone.
Attacks that exploit this kind of access
The rule that runs TRELLO_DELETE_MEMBER_CUSTOM_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_MEMBER_CUSTOM_STICKER, this is the rule to start with:
TRELLO_DELETE_MEMBER_CUSTOM_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_MEMBER_CUSTOM_STICKER call is checked against it from then on.
Questions about TRELLO_DELETE_MEMBER_CUSTOM_STICKER
Deletes a custom sticker from a Trello member's collection; this permanent action is only available for custom stickers within a Trello Workspace on a paid plan. 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_MEMBER_CUSTOM_STICKER accepts 2 parameters: idMember, idCustomSticker. 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_MEMBER_CUSTOM_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_MEMBER_CUSTOM_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_MEMBER_CUSTOM_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_MEMBER_CUSTOM_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_MEMBER_CUSTOM_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