TRELLO_ADD_NOTIFICATIONS_ALL_READ
Marks all Trello notifications for the authenticated user as read across all boards; this action is permanent and cannot be undone.
This record as markdown: /tools/trello/trello-add-notifications-all-read.md
What TRELLO_ADD_NOTIFICATIONS_ALL_READ does on Trello
AI agents call TRELLO_ADD_NOTIFICATIONS_ALL_READ to permanently remove resources in Trello, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why TRELLO_ADD_NOTIFICATIONS_ALL_READ is rated Critical
Although the tool doesn't delete data in the traditional sense, marking notifications as read is irreversible and destroys the unread status information permanently. This fits the Destructive category as it cannot be undone and represents loss of state.
From the tool's definition Description explicitly states 'this action is permanent and cannot be undone.' The tool modifies notification state in a way that irreversibly discards unread status across all notifications.
Attacks that exploit this kind of access
The rule that runs TRELLO_ADD_NOTIFICATIONS_ALL_READ 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_ADD_NOTIFICATIONS_ALL_READ, this is the rule to start with:
TRELLO_ADD_NOTIFICATIONS_ALL_READ is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Trello, apply this rule, and every TRELLO_ADD_NOTIFICATIONS_ALL_READ call is checked against it from then on.
Questions about TRELLO_ADD_NOTIFICATIONS_ALL_READ
Marks all Trello notifications for the authenticated user as read across all boards; this action is permanent and cannot be undone. It is categorised as a Destructive tool in the Trello MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trello MCP server in PolicyLayer and add a rule for TRELLO_ADD_NOTIFICATIONS_ALL_READ: 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_ADD_NOTIFICATIONS_ALL_READ is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the TRELLO_ADD_NOTIFICATIONS_ALL_READ 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_ADD_NOTIFICATIONS_ALL_READ. 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_ADD_NOTIFICATIONS_ALL_READ 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.
Across the catalogue