TRELLO_GET_MEMBER_CUSTOM_STICKER
Retrieves a specific custom sticker by ID for a Trello member; returns only sticker data (not its usage on cards/boards), with optional field selection.
This record as markdown: /tools/trello/trello-get-member-custom-sticker.md
What TRELLO_GET_MEMBER_CUSTOM_STICKER does on Trello
AI agents call TRELLO_GET_MEMBER_CUSTOM_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 the fields to return for the custom sticker. Use 'all' (default) to return all fields, or provide a comma-separated list containing 'scaled' or 'url'. |
idMember | string | — | The ID or username of the Trello member. |
idCustomSticker | string | — | The ID of the custom sticker to retrieve. |
Parameters from the server's own tool schema.
Why TRELLO_GET_MEMBER_CUSTOM_STICKER is rated Low
This tool performs a data retrieval operation with no capability to modify, delete, or execute actions. It fetches metadata about a custom sticker resource for a Trello member. The scope is limited to sticker information only, and the operation is read-only. Severity is low because disclosure of sticker metadata poses minimal security or business risk.
From the tool's definition Tool description states 'Retrieves a specific custom sticker by ID' and explicitly clarifies it 'returns only sticker data (not its usage on cards/boards)', indicating a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs TRELLO_GET_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_GET_MEMBER_CUSTOM_STICKER, this is the rule to start with:
TRELLO_GET_MEMBER_CUSTOM_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_MEMBER_CUSTOM_STICKER call is checked against it from then on.
Questions about TRELLO_GET_MEMBER_CUSTOM_STICKER
Retrieves a specific custom sticker by ID for a Trello member; returns only sticker data (not its usage on cards/boards), with optional field selection. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.
TRELLO_GET_MEMBER_CUSTOM_STICKER accepts 3 parameters: fields, 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_GET_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_GET_MEMBER_CUSTOM_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_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_GET_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_GET_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.
This server
Across the catalogue