TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER
Call this action to retrieve detailed properties (like image, position, rotation) of a specific sticker on a Trello card.
This record as markdown: /tools/trello/trello-get-cards-stickers-by-id-card-by-id-sticker.md
What TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER does on Trello
AI agents call TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER to retrieve information from Trello without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fields | string | — | Specifies sticker fields to return (e.g., 'image,top,left'). Allowed: 'image', 'imageScaled', 'imageUrl', 'left', 'rotate', 'top', 'zIndex'. Use 'all' (default) |
idCard | string | — | The ID or shortLink of the Trello card to which the sticker belongs. |
idSticker | string | — | The ID of the sticker to retrieve. |
Parameters from the server's own tool schema.
Why TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER is rated Low
This tool retrieves sticker metadata (image, position, rotation) from an existing Trello card. It performs a simple data query with no ability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only view sticker information that already exists.
From the tool's definition The tool description explicitly states it is used to "retrieve detailed properties" of a sticker, which is a read-only query operation with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs TRELLO_GET_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_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER, this is the rule to start with:
TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER is read-only, so it stays allowed. 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_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER call is checked against it from then on.
Questions about TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER
Call this action to retrieve detailed properties (like image, position, rotation) of a specific sticker on a Trello card. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.
TRELLO_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER accepts 3 parameters: fields, 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_GET_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_GET_CARDS_STICKERS_BY_ID_CARD_BY_ID_STICKER is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the TRELLO_GET_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_GET_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_GET_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.
This server
Across the catalogue