Update an existing Trello card. Only provided fields will be changed. This tool can also move a card by setting idList and/or idBoard. Args: - card_id (string): The card to update (required) - name (string, optional): New card title - desc (string, optional): New description - closed (boolean, op...
AI agents use trello_update_card to create or update resources in Trello MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello MCP Server environment.
This is a Write operation—it creates or modifies data reversibly. While the tool can archive cards (setting 'closed' to true), this is archiving rather than permanent deletion and is reversible by unarchiving. The severity is medium because misuse could disrupt workflow by moving/renaming many cards, but no data is permanently lost and actions are fully reversible through standard Trello operations.
From the tool's definition Tool performs card updates and modifications: 'Update an existing Trello card. Only provided fields will be changed.' Supports reversible operations including renaming ('name'), editing descriptions ('desc'), archiving ('closed'), and moving cards ('idList',…
Attacks that exploit this kind of access
Update an existing Trello card. Only provided fields will be changed. This tool can also move a card by setting idList and/or idBoard. Args: - card_id (string): The card to update (required) - name (string, optional): New card title - desc (string, optional): New description - closed (boolean, optional): true to archive, false to unarchive - idList (string, optional): Move card to this list - idBoard (string, optional): Move card to this board (also provide idList) - pos (. It is categorised as a Write tool in the Trello MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello MCP Server MCP server in PolicyLayer and add a rule for trello_update_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 MCP Server. Nothing to install.
trello_update_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_update_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_update_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_update_card is provided by the Trello MCP Server MCP server (rdeprey/trello-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →