import_transactions · Actual Budget MCP Server MCP

WHAT IT DOES

What import_transactions does on Actual Budget MCP Server

AI agents use import_transactions to create or update resources in Actual Budget MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Actual Budget MCP Server environment.

WHY IT NEEDS A POLICY

Why import_transactions needs a policy

The tool creates multiple transaction records in a financial management system. While it modifies financial data, it does not move money or create financial obligations (thus not Financial), is not destructive/irreversible (duplicates are detected, transactions can be edited or deleted via sibling tools), and does not execute arbitrary code.

From the tool's definition Tool performs batch import of transactions, which creates or modifies financial records. Description states 'Import multiple transactions' and 'Supports imported_id for duplicate detection', indicating write operations that add data to the budget system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_transactions Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_transactions": {
      "limits": [
        {
          "counter": "import_transactions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Actual Budget MCP Server, so you can run agents against it safely.

FAQ

Questions about import_transactions

What does the import_transactions tool do? +

Import multiple transactions in a single batch operation. More efficient than individual add_transaction calls. Supports imported_id for duplicate detection and automatic rule application. It is categorised as a Write tool in the Actual Budget MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_transactions? +

Register the Actual Budget MCP Server 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 Budget MCP Server. Nothing to install.

What risk level is import_transactions? +

import_transactions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_transactions? +

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.

How do I block import_transactions completely? +

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.

What MCP server provides import_transactions? +

import_transactions is provided by the Actual Budget MCP Server MCP server (yhc0712/actual-budget-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.