cost_trend
Use this when the user wants to see monthly spend over time (e.g. 'Show me my cost trend', 'How has my spend changed over the last 6 months?'). Returns monthly cost data points, optionally broken down by service/project/cloud. The last point is the partial current month; months=1 means month-to-d...
This record as markdown: /tools/doit/cost-trend.md
What cost_trend does on Doit
AI agents call cost_trend 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 |
|---|---|---|---|
topN | integer | — | When groupBy is set, select top-N groups by total cost across the range (default 5, max 25), not a row cap. |
cloud | string | — | Filter to a specific cloud provider. Accepts aliases like "aws", "gcp", "azure". |
months | integer | — | Number of calendar months, 1–36 (default 6): N-1 complete months plus the partial current month-to-date. |
groupBy | string | — | Optional breakdown dimension. If omitted the trend is a single total line. |
Parameters from the server's own tool schema.
Why cost_trend is rated Low
Even though cost_trend 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 cost_trend 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 cost_trend, this is the rule to start with:
cost_trend 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 cost_trend call is checked against it from then on.
Questions about cost_trend
Use this when the user wants to see monthly spend over time (e.g. 'Show me my cost trend', 'How has my spend changed over the last 6 months?'). Returns monthly cost data points, optionally broken down by service/project/cloud. The last point is the partial current month; months=1 means month-to-date. For daily granularity or custom time intervals, use run_query instead. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
cost_trend accepts 4 parameters: topN, cloud, months, groupBy. 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 cost_trend: 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.
cost_trend 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 cost_trend 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 cost_trend. 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.
cost_trend 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