list_budgets
Use this when the user wants to see their cloud spending budgets or check budget status. Returns a paginated list of budgets with names, amounts, and utilization. Do NOT use this for cost analysis (use run_query) or spending alerts (use list_alerts).
This record as markdown: /tools/doit/list-budgets.md
What list_budgets does on Doit
AI agents call list_budgets to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Server-side case-insensitive substring filter on budget names, applied before pagination (nameContains). |
filter | string | — | An expression for filtering the results. Syntax: "key:value". Available keys: owner, budgetName, lastModified in ms (at or after; also orders by update time), r |
pageToken | string | — | Page token, returned by a previous call, to request the next page of results. |
maxResults | string | — | The maximum number of results to return in a single page. Defaults to 50; maximum 250 (larger values are rejected). |
maxCreationTime | string | — | Max value for budget creation time, in milliseconds since the POSIX epoch. Only budgets created before or at this timestamp are returned. |
minCreationTime | string | — | Min value for budget creation time, in milliseconds since the POSIX epoch. Only budgets created after or at this timestamp are returned. |
Parameters from the server's own tool schema.
Why list_budgets is rated Low
Even though list_budgets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_budgets 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 list_budgets, this is the rule to start with:
list_budgets is read-only, so it stays allowed. 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 list_budgets call is checked against it from then on.
Questions about list_budgets
Use this when the user wants to see their cloud spending budgets or check budget status. Returns a paginated list of budgets with names, amounts, and utilization. Do NOT use this for cost analysis (use run_query) or spending alerts (use list_alerts). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
list_budgets accepts 6 parameters: name, filter, pageToken, maxResults, maxCreationTime, minCreationTime. 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 list_budgets: 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.
list_budgets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_budgets 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 list_budgets. 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.
list_budgets 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