TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD
Assigns a Trello member to a specific Trello card by card ID (or short link) and member ID.
This record as markdown: /tools/trello/trello-add-cards-id-members-by-id-card.md
What TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD does on Trello
AI agents use TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD to create or update resources in Trello, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
value | string | — | The ID of the Trello member to be added to the card. |
idCard | string | — | The ID or short link of the Trello card to which the member will be added. |
Parameters from the server's own tool schema.
Why TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD is rated Medium
This tool modifies card state by adding a member assignment, which is a create/update operation with no destructive or financial implications. The change is reversible (a member can be unassigned). While it affects board collaboration, the blast radius of misuse is limited to card assignments and team visibility—no data is deleted, no financial transactions occur, and no arbitrary code execution is involved.
From the tool's definition Tool description states it "Assigns a Trello member to a specific Trello card", which is a modification operation that creates a relationship between a member and a card.
Attacks that exploit this kind of access
The rule that runs TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD 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_CARDS_ID_MEMBERS_BY_ID_CARD, this is the rule to start with:
TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_ADD_CARDS_ID_MEMBERS_BY_ID_CARD call is checked against it from then on.
Questions about TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD
Assigns a Trello member to a specific Trello card by card ID (or short link) and member ID. It is categorised as a Write tool in the Trello MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD accepts 2 parameters: value, idCard. 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_ADD_CARDS_ID_MEMBERS_BY_ID_CARD: 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_CARDS_ID_MEMBERS_BY_ID_CARD is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD 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_CARDS_ID_MEMBERS_BY_ID_CARD. 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_CARDS_ID_MEMBERS_BY_ID_CARD 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