update_budget

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-budget.md

WHAT IT DOES

What update_budget does on Doit

AI agents use update_budget 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 budget to update (required).
`name`	string	—	Budget name. Must be non-empty if provided.
`type`	string	—	Budget type. If supplied, fixed requires endPeriod and recurring requires timeInterval. Accepted values: fixed, recurring.
`scope`	array	—	List of allocations that define the budget scope (deprecated). Cannot be combined with scopes.
`alerts`	array	—	List of up to three alert thresholds defined as a percentage of the amount.
`amount`	number	—	Budget period amount; required when usePrevSpend is explicitly false. Omitted means unchanged.
`metric`	string	—	Budget metric: cost or amortized_cost; omitted means unchanged.
`public`	string	—	Public sharing access level. Accepted values: owner, editor, viewer.
`scopes`	array	—	Filters that define the scope of the budget. Cannot be combined with scope.
`currency`	string	—	Currency code. Accepted values: USD, ILS, EUR, AUD, CAD, GBP, DKK, NOK, SEK, BRL, SGD, MXN, CHF, MYR, TWD, EGP, ZAR, JPY, IDR, AED, THB, COP.
`endPeriod`	integer	—	Fixed budget end date as a UNIX timestamp in milliseconds. Required when setting type to fixed; must not be set for recurring budgets.
`recipients`	array	—	List of email addresses to notify when reaching an alert threshold.

Parameters from the server's own tool schema.

RISK

Why update_budget is rated Medium

An AI agent can call update_budget 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 (34 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_budget 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_budget, this is the rule to start with:

update_budget Rate-limited

update_budget 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_budget": {
      "limits": [
        {
          "counter": "update_budget_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every update_budget call is checked against it from then on.

FAQ

Questions about update_budget

What does the update_budget tool do? +

Use this when the user wants to modify an existing budget. Supports partial updates; omitted fields retain their current values. Setting type to fixed requires endPeriod; setting type to recurring requires timeInterval and forbids endPeriod; setting usePrevSpend to false requires amount. Changes apply immediately. Do NOT use this for viewing budgets (use list_budgets) or creating new budgets (use create_budget). 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.

What parameters does update_budget accept? +

update_budget accepts 12 parameters: id, name, type, scope, alerts, amount, metric, public, scopes, currency, endPeriod, recipients. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_budget? +

Register the Doit MCP server in PolicyLayer and add a rule for update_budget: 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.

What risk level is update_budget? +

update_budget is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_budget? +

Yes. Add a rate_limit block to the update_budget 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.

How do I block update_budget completely? +

Set action: deny in the PolicyLayer policy for update_budget. 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.

What MCP server provides update_budget? +

update_budget 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.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →