Update properties of an existing Trello card. Use this to change card details like name, description, due date, or status.
AI agents use update_card to create or update resources in Trello Desktop MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello Desktop MCP environment.
This tool modifies existing data (card properties) but does not delete or destroy anything. Changes to card metadata are reversible—names, descriptions, dates, and status can all be updated again or reverted. This fits squarely in the Write category.
From the tool's definition Tool description states it 'Update[s] properties of an existing Trello card' and can 'change card details like name, description, due date, or status.' These are reversible modifications to data.
Documented attack patterns abuse exactly the kind of access update_card gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trello Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_card:
{
"version": "1",
"default": "deny",
"tools": {
"update_card": {
"limits": [
{
"counter": "update_card_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_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.
Free to start. No card required.
Update properties of an existing Trello card. Use this to change card details like name, description, due date, or status. It is categorised as a Write tool in the Trello Desktop MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello Desktop MCP server in PolicyLayer and add a rule for 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 Desktop MCP. Nothing to install.
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 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 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.
update_card is provided by the Trello Desktop MCP server (kocakli/trello-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trello Desktop MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Trello Desktop MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.