TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER
Permanently removes a current member from a Trello board, revoking their access; this action is irreversible.
This record as markdown: /tools/trello/trello-delete-boards-members-by-id-board-by-id-member.md
What TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER does on Trello
AI agents call TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
idBoard | string | — | The ID of the board from which the member will be removed. |
idMember | string | — | The ID of the member to remove from the board. |
Parameters from the server's own tool schema.
Why TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER is rated Critical
This tool permanently deletes a member's access to a board with no undo capability. While not data deletion in the traditional sense, it irreversibly destroys a relationship/permission state, which cannot be reversed by the AI agent—the removed member must be manually re-added by a board admin.
From the tool's definition Tool description states "Permanently removes a current member from a Trello board, revoking their access; this action is irreversible." The keywords "Permanently removes" and "irreversible" clearly indicate an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER, this is the rule to start with:
TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER call is checked against it from then on.
Questions about TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER
Permanently removes a current member from a Trello board, revoking their access; this action is irreversible. 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.
TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER accepts 2 parameters: idBoard, idMember. 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER: 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER. 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_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER 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