update_label
Use this when the user wants to modify an existing custom DoiT console label. Requires Cloud Analytics Admin; preset labels cannot be edited. Supports partial updates; null leaves a field unchanged. Changes apply immediately. Do NOT use this for creating new labels (use create_label) or annotatio...
This record as markdown: /tools/doit/update-label.md
What update_label does on Doit
AI agents use update_label to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The ID of the label to update (required). |
name | object | — | The name of the label. Must be non-empty and unique if provided; omission or null leaves unchanged. |
color | object | — | The color of the label. Accepted values: blue, skyBlue, teal, mint, lime, softYellow, apricot, lavender, purple, rosePink, slateGrey. Omission or null leaves un |
Parameters from the server's own tool schema.
Why update_label is rated Medium
An AI agent can call update_label faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs update_label safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_label, this is the rule to start with:
update_label 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 Doit, apply this rule, and every update_label call is checked against it from then on.
Questions about update_label
Use this when the user wants to modify an existing custom DoiT console label. Requires Cloud Analytics Admin; preset labels cannot be edited. Supports partial updates; null leaves a field unchanged. Changes apply immediately. Do NOT use this for creating new labels (use create_label) or annotations (use update_annotation). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_label accepts 3 parameters: id, name, color. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for update_label: 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 Doit. Nothing to install.
update_label 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 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. 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 is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue