This record as markdown: /tools/actual/actual-budgets-holdfornextmonth.md
What actual_budgets_holdForNextMonth does on Actual
AI agents use actual_budgets_holdForNextMonth to create or update resources in Actual, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Actual environment.
Why actual_budgets_holdForNextMonth is rated Medium
This tool modifies budget allocation by holding funds for the next month. This is a reversible financial data modification (budget adjustment), not a direct money movement or payment. It writes/updates budget state within the Actual Budget application rather than executing real financial transactions.
From the tool's definition Hold an amount from this month
Attacks that exploit this kind of access
The rule that runs actual_budgets_holdForNextMonth 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_holdForNextMonth, this is the rule to start with:
actual_budgets_holdForNextMonth 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 Actual, apply this rule, and every actual_budgets_holdForNextMonth call is checked against it from then on.
Questions about actual_budgets_holdForNextMonth
Hold an amount from this month. It is categorised as a Write tool in the Actual MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Actual MCP server in PolicyLayer and add a rule for actual_budgets_holdForNextMonth: 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_holdForNextMonth 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 actual_budgets_holdForNextMonth 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_holdForNextMonth. 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_holdForNextMonth 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