update_allocation
Use this when the user wants to modify an existing cost allocation. Omitted fields are preserved. Use rule for an existing single allocation and rules for an existing group; the type cannot change. A supplied rules list replaces the entire group membership. Changes apply immediately. Do NOT use t...
This record as markdown: /tools/doit/update-allocation.md
What update_allocation does on Doit
AI agents use update_allocation 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 allocation to update |
name | string | — | New name; omit to keep the current name. |
rule | object | — | A single allocation rule that defines one grouping. Provide this for a single-rule allocation. Mutually exclusive with 'rules' |
rules | array | — | Ordered list of at least two group rules. create creates a rule, update edits a rule, select includes it unchanged. On update this replaces the entire list; inc |
description | string | — | Description of the allocation. On update omission or an empty string preserves the stored description; the API does not support clearing it |
unallocatedCosts | string | null | — | Group-only label for unmatched costs. On update omission or null preserves the stored label; a string updates it independently of rules |
Parameters from the server's own tool schema.
Why update_allocation is rated Medium
An AI agent can call update_allocation 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 signalsHigh parameter count (14 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs update_allocation 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_allocation, this is the rule to start with:
update_allocation 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_allocation call is checked against it from then on.
Questions about update_allocation
Use this when the user wants to modify an existing cost allocation. Omitted fields are preserved. Use rule for an existing single allocation and rules for an existing group; the type cannot change. A supplied rules list replaces the entire group membership. Changes apply immediately. Do NOT use this for creating new allocations (use create_allocation) or viewing allocations (use list_allocations). 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_allocation accepts 6 parameters: id, name, rule, rules, description, unallocatedCosts. 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_allocation: 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_allocation 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_allocation 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_allocation. 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_allocation 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