actual_rules_update
Update an existing budget rule by ID. Only provide the fields you want to change. IMPORTANT Field Types: -
This record as markdown: /tools/actual/actual-rules-update.md
What actual_rules_update does on Actual
AI agents use actual_rules_update 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_rules_update is rated Medium
This tool creates or modifies data (budget rules) in a reversible manner. While it operates in a financial management context (Actual Budget), it does not move money, commit financial obligations, or execute arbitrary operations—it only updates rule configuration. This is Write rather than Financial because the primary action is data modification, not monetary movement.
From the tool's definition Tool description states 'Update an existing budget rule' — modifies data reversibly. The tool name 'actual_rules_update' and description explicitly indicate modification of budget rules, which are configuration objects in a financial management system.
Attacks that exploit this kind of access
The rule that runs actual_rules_update 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_rules_update, this is the rule to start with:
actual_rules_update 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_rules_update call is checked against it from then on.
Questions about actual_rules_update
Update an existing budget rule by ID. Only provide the fields you want to change. IMPORTANT Field Types: -. 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_rules_update: 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_rules_update 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_rules_update 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_rules_update. 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_rules_update 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