High Risk →

run-bank-sync

Run bank synchronization (GoCardless/SimpleFIN) to download latest transactions.

How to control run-bank-sync ↓

AI agents invoke run-bank-sync to trigger actions in Actual. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

This tool executes a synchronization process with external financial systems to download transactions. While not directly moving money, it initiates automated actions against third-party APIs with side effects (pulling/importing financial data into Actual Budget). It requires triggering external operations, making it Execute rather than Read.

From the tool's definition Tool description states it 'Run[s] bank synchronization' which triggers an external operation (GoCardless/SimpleFIN API calls) whose effects depend on runtime state and credentials.

Documented attack patterns abuse exactly the kind of access run-bank-sync 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 run-bank-sync:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run-bank-sync": {
      "limits": [
        {
          "counter": "run-bank-sync_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run-bank-sync stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Actual — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the run-bank-sync tool do? +

Run bank synchronization (GoCardless/SimpleFIN) to download latest transactions. It is categorised as a Execute tool in the Actual MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run-bank-sync? +

Register the Actual MCP server in PolicyLayer and add a rule for run-bank-sync: 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.

What risk level is run-bank-sync? +

run-bank-sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run-bank-sync? +

Yes. Add a rate_limit block to the run-bank-sync 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 run-bank-sync completely? +

Set action: deny in the PolicyLayer policy for run-bank-sync. 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 run-bank-sync? +

run-bank-sync 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.

Enforce policy on every Actual tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.