assign_objects_to_label
Use this when the user wants to assign or unassign DoiT console objects (reports, budgets, alerts, allocations, metrics or annotations) to a custom console label. Preset labels cannot be assigned. Requires edit permission on every object; validation is all-or-nothing. add/remove modify associatio...
This record as markdown: /tools/doit/assign-objects-to-label.md
What assign_objects_to_label does on Doit
AI agents use assign_objects_to_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 assign or unassign objects to. |
add | array | — | Array of objects to assign to the label. Each object must have objectId and objectType. |
remove | array | — | Array of objects to unassign from the label. Each object must have objectId and objectType. |
Parameters from the server's own tool schema.
Why assign_objects_to_label is rated Medium
An AI agent can call assign_objects_to_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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs assign_objects_to_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 assign_objects_to_label, this is the rule to start with:
assign_objects_to_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 assign_objects_to_label call is checked against it from then on.
Questions about assign_objects_to_label
Use this when the user wants to assign or unassign DoiT console objects (reports, budgets, alerts, allocations, metrics or annotations) to a custom console label. Preset labels cannot be assigned. Requires edit permission on every object; validation is all-or-nothing. add/remove modify associations, not a replacement list. Changes apply immediately. Do NOT use this for creating labels (use create_label) or viewing assignments (use get_label_assignments). 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.
assign_objects_to_label accepts 3 parameters: id, add, remove. 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 assign_objects_to_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.
assign_objects_to_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 assign_objects_to_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 assign_objects_to_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.
assign_objects_to_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