actual_budgets_getMonths
Get a list of all available budget months with summary data. Returns an array of months showing total budgeted, spent, and income for each month. Useful for viewing budget history and trends over time.
This record as markdown: /tools/actual/actual-budgets-getmonths.md
What actual_budgets_getMonths does on Actual
AI agents call actual_budgets_getMonths to retrieve information from Actual without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why actual_budgets_getMonths is rated Low
This tool only queries and retrieves historical budget data for viewing and analysis purposes. It has no side effects, does not execute code or commands, does not create, modify, or delete data, and does not move money or create financial obligations. It is a straightforward Read operation with minimal security risk in isolation, though the context is a financial management system.
From the tool's definition Tool retrieves 'a list of all available budget months with summary data' and is described as 'useful for viewing budget history and trends' — a query operation with no modifications, deletions, or financial transactions.
Attacks that exploit this kind of access
The rule that runs actual_budgets_getMonths safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Actual, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For actual_budgets_getMonths, this is the rule to start with:
actual_budgets_getMonths 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 Actual, apply this rule, and every actual_budgets_getMonths call is checked against it from then on.
Questions about actual_budgets_getMonths
Get a list of all available budget months with summary data. Returns an array of months showing total budgeted, spent, and income for each month. Useful for viewing budget history and trends over time. It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.
Register the Actual MCP server in PolicyLayer and add a rule for actual_budgets_getMonths: 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 Actual. Nothing to install.
actual_budgets_getMonths 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 actual_budgets_getMonths 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 actual_budgets_getMonths. 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.
actual_budgets_getMonths is provided by the Actual MCP server (actual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Actual, and thousands of servers like it.
This server
Across the catalogue