actual_accounts_close
Mark an account as closed in Actual Budget. Closed accounts are hidden from most views but their transaction history is preserved. Useful for accounts that are no longer active but you want to keep the historical data.
This record as markdown: /tools/actual/actual-accounts-close.md
What actual_accounts_close does on Actual
AI agents use actual_accounts_close 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_accounts_close is rated Medium
The tool modifies account state by marking it as closed, which is a Write category operation. It is reversible (accounts can be reopened via actual_accounts_reopen), so it does not qualify as Destructive. The severity is medium because closing an account could hide important financial data from views and impact financial workflows, but the preserved transaction history and reversibility limit the damage.
From the tool's definition Tool description states it 'Mark an account as closed' which is a state modification. The description explicitly notes that 'Closed accounts are hidden from most views but their transaction history is preserved,' confirming this is a reversible change…
Attacks that exploit this kind of access
The rule that runs actual_accounts_close 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_accounts_close, this is the rule to start with:
actual_accounts_close 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_accounts_close call is checked against it from then on.
Questions about actual_accounts_close
Mark an account as closed in Actual Budget. Closed accounts are hidden from most views but their transaction history is preserved. Useful for accounts that are no longer active but you want to keep the historical data. 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_accounts_close: 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_accounts_close 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_accounts_close 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_accounts_close. 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_accounts_close 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