create_label
Use this when the user wants to create a new DoiT console label for organizing analytics objects. Names must be unique within the customer. Requires Cloud Analytics Admin. Changes apply immediately. Do NOT use this for viewing existing labels (use list_labels) or annotations (use create_annotation).
This record as markdown: /tools/doit/create-label.md
What create_label does on Doit
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | The name of the label (required, non-empty). |
color | string | Yes | The color of the label (required). Accepted values: blue, skyBlue, teal, mint, lime, softYellow, apricot, lavender, purple, rosePink, slateGrey. |
Parameters from the server's own tool schema.
Why create_label is rated Medium
An AI agent can call create_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 create_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 create_label, this is the rule to start with:
create_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 create_label call is checked against it from then on.
Questions about create_label
Use this when the user wants to create a new DoiT console label for organizing analytics objects. Names must be unique within the customer. Requires Cloud Analytics Admin. Changes apply immediately. Do NOT use this for viewing existing labels (use list_labels) or annotations (use create_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.
create_label accepts 2 parameters: name, color. Required: name, color. 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 create_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.
create_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 create_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 create_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.
create_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