Import a list of transactions into an account using reconciliation logic.
AI agents use import-transactions 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.
This tool creates new transaction records in Actual Budget, making it a Write operation. While it affects financial data, it does not move money (Financial category) nor irreversibly delete data (Destructive). However, severity is high because misuse could flood accounts with false transactions, corrupt budget reconciliation, or create fraudulent entries that are difficult to untangle, even if technically reversible.
From the tool's definition Tool description states 'Import a list of transactions into an account' which creates new financial records in the budget system.
Documented attack patterns abuse exactly the kind of access import-transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Actual, and nothing reaches the server without passing your rules. This is the rule we recommend for import-transactions:
{
"version": "1",
"default": "deny",
"tools": {
"import-transactions": {
"limits": [
{
"counter": "import-transactions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import-transactions 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.
Free to start. No card required.
Import a list of transactions into an account using reconciliation logic. 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 import-transactions: 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.
import-transactions 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 import-transactions 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 import-transactions. 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.
import-transactions is provided by the Actual MCP server (s-stefanov/actual-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Actual tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Actual tools catalogued and risk-classified — across an index of 42,500+ MCP servers.