TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION
Retrieves a specific Trello notification by its ID, optionally including related entities and specific fields for the notification and its related entities.
This record as markdown: /tools/trello/trello-get-notifications-by-id-notification.md
What TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION does on Trello
AI agents call TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION 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 |
|---|---|---|---|
card | string | — | Whether to include the associated card. Accepts 'true' or 'false'. |
list | string | — | Whether to include the associated list. Accepts 'true' or 'false'. |
board | string | — | Whether to include the associated board. Accepts 'true' or 'false'. |
fields | string | — | Fields for the notification: 'all' or a comma-separated list (e.g., data,date,type). Available: data, date, idMemberCreator, type, unread. Default: 'all'. |
member | string | — | Whether to include the associated member (distinct from memberCreator). Accepts 'true' or 'false'. |
display | string | — | Whether to include the notification display status. Accepts 'true' or 'false'. |
entities | string | — | Whether to include associated entities (like cards, boards, members). Accepts 'true' or 'false'. |
card_fields | string | — | Fields for the card: 'all' or a comma-separated list (e.g., name,due). Available: badges, checkItemStates, closed, dateLastActivity, desc, descData, due, email, |
board_fields | string | — | Fields for the board: 'all' or a comma-separated list (e.g., name,url). Available: closed, dateLastActivity, dateLastView, desc, descData, idOrganization, invit |
organization | string | — | Whether to include the associated organization. Accepts 'true' or 'false'. |
memberCreator | string | — | Whether to include the member who created the notification. Accepts 'true' or 'false'. |
member_fields | string | — | Fields for the associated member: 'all' or a comma-separated list (e.g., fullName,initials). Available: avatarHash, bio, bioData, confirmed, fullName, idPremOrg |
Parameters from the server's own tool schema.
Why TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION is rated Low
The tool only performs a retrieval operation on existing notification data. It does not create, modify, delete, or execute any actions. The parameters allow filtering and field selection for the response, but these are read-only query options. The blast radius of misuse is minimal—an agent could only over-retrieve notifications they may already have access to, posing no irreversible or harmful impact.
From the tool's definition Tool description states it 'Retrieves a specific Trello notification by its ID' — this is a query operation with no side effects or data modification.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION 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_NOTIFICATIONS_BY_ID_NOTIFICATION, this is the rule to start with:
TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION 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_NOTIFICATIONS_BY_ID_NOTIFICATION call is checked against it from then on.
Questions about TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION
Retrieves a specific Trello notification by its ID, optionally including related entities and specific fields for the notification and its related entities. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.
TRELLO_GET_NOTIFICATIONS_BY_ID_NOTIFICATION accepts 12 parameters: card, list, board, fields, member, display, entities, card_fields, board_fields, organization, memberCreator, member_fields. 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_NOTIFICATIONS_BY_ID_NOTIFICATION: 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_NOTIFICATIONS_BY_ID_NOTIFICATION 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_NOTIFICATIONS_BY_ID_NOTIFICATION 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_NOTIFICATIONS_BY_ID_NOTIFICATION. 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_NOTIFICATIONS_BY_ID_NOTIFICATION 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