actual_transactions_import
Bulk import transactions with automatic reconciliation and duplicate detection. Matches against existing transactions using imported_id to prevent duplicates. Ideal for importing bank statements, CSV files, or syncing from external sources. Automatically applies budget rules.
This record as markdown: /tools/actual/actual-transactions-import.md
What actual_transactions_import does on Actual
AI agents use actual_transactions_import 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_transactions_import is rated Medium
While this tool modifies financial data (which could be considered Execute-like in effect), it is fundamentally a Write operation—it creates or updates transaction records in the budget database reversibly. It is not Destructive because imports can be reversed or corrected.
From the tool's definition Tool description explicitly states 'Bulk import transactions' and 'automatically applies budget rules', which creates and modifies financial data in the system.
Attacks that exploit this kind of access
The rule that runs actual_transactions_import 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_transactions_import, this is the rule to start with:
actual_transactions_import 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_transactions_import call is checked against it from then on.
Questions about actual_transactions_import
Bulk import transactions with automatic reconciliation and duplicate detection. Matches against existing transactions using imported_id to prevent duplicates. Ideal for importing bank statements, CSV files, or syncing from external sources. Automatically applies budget rules. 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_transactions_import: 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_transactions_import 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_transactions_import 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_transactions_import. 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_transactions_import 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