TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL
Removes a specific label from a Trello card; the label itself is not deleted from the board, only its association with the card.
This record as markdown: /tools/trello/trello-delete-cards-id-labels-by-id-card-by-id-label.md
What TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL does on Trello
AI agents use TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
idCard | string | — | The ID or short link of the card from which the label will be removed. |
idLabel | string | — | The ID of the label to be removed from the card. |
Parameters from the server's own tool schema.
Why TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL is rated Medium
Although the tool name contains 'DELETE', the description clarifies it only removes the association between a label and a card — the label itself is not deleted. This is a reversible modification (the label can be re-added), making it a Write operation rather than Destructive.
From the tool's definition Removes a specific label from a Trello card; the label itself is not deleted from the board, only its association with the card.
Attacks that exploit this kind of access
The rule that runs TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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_ID_LABELS_BY_ID_CARD_BY_ID_LABEL, this is the rule to start with:
TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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 TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL call is checked against it from then on.
Questions about TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL
Removes a specific label from a Trello card; the label itself is not deleted from the board, only its association with the card. 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.
TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL accepts 2 parameters: idCard, idLabel. 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_ID_LABELS_BY_ID_CARD_BY_ID_LABEL: 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_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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 TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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_ID_LABELS_BY_ID_CARD_BY_ID_LABEL. 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_ID_LABELS_BY_ID_CARD_BY_ID_LABEL 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.
This server
Across the catalogue