Update the color of a label. Use this tool to change the color of a label.
AI agents use update_label_color 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.
Updating a label's color is a reversible modification operation that changes data but does not create, delete, or execute external code. It falls squarely in the Write category. Severity is low because changing a label color has minimal blast radius—it affects visual organization only and can be easily undone or reverted.
From the tool's definition Tool description states "Update the color of a label" and "change the color of a label" — this modifies existing label metadata (color property) reversibly without deleting or destroying data.
Documented attack patterns abuse exactly the kind of access update_label_color gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trello, and nothing reaches the server without passing your rules. This is the rule we recommend for update_label_color:
{
"version": "1",
"default": "deny",
"tools": {
"update_label_color": {
"limits": [
{
"counter": "update_label_color_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_label_color 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 the color of a label. Use this tool to change the color of a label. 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.
Register the Trello MCP server in PolicyLayer and add a rule for update_label_color: 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.
update_label_color 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_label_color 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_label_color. 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_label_color is provided by the Trello MCP server (v4lheru/trello-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trello, 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.
76 Trello tools catalogued and risk-classified — across an index of 43,000+ MCP servers.