TRELLO_GET_MEMBER_CUSTOM_EMOJI
Retrieves a specific custom emoji by its ID for a Trello member, requiring that both the member and emoji exist and are associated.
This record as markdown: /tools/trello/trello-get-member-custom-emoji.md
What TRELLO_GET_MEMBER_CUSTOM_EMOJI does on Trello
AI agents call TRELLO_GET_MEMBER_CUSTOM_EMOJI 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 | — | Determines which fields to include in the response for the custom emoji. Valid values are 'all' or a comma-separated list of field names (e.g., 'name', 'url'). |
idMember | string | — | The ID or username of the Trello member. This identifies the owner of the custom emoji. |
idCustomEmoji | string | — | The ID of the custom emoji to be retrieved. |
Parameters from the server's own tool schema.
Why TRELLO_GET_MEMBER_CUSTOM_EMOJI is rated Low
This tool performs a read-only query operation to fetch emoji data associated with a Trello member. It retrieves information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only view emoji metadata that a member has access to.
From the tool's definition Tool name contains 'GET' and description states 'Retrieves a specific custom emoji by its ID' with no mention of modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs TRELLO_GET_MEMBER_CUSTOM_EMOJI 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_EMOJI, this is the rule to start with:
TRELLO_GET_MEMBER_CUSTOM_EMOJI 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_EMOJI call is checked against it from then on.
Questions about TRELLO_GET_MEMBER_CUSTOM_EMOJI
Retrieves a specific custom emoji by its ID for a Trello member, requiring that both the member and emoji exist and are associated. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.
TRELLO_GET_MEMBER_CUSTOM_EMOJI accepts 3 parameters: fields, idMember, idCustomEmoji. 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_EMOJI: 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_EMOJI 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_EMOJI 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_EMOJI. 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_EMOJI 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