actual_payees_merge

Merge one or more payees into a target payee. This consolidates duplicate payees by merging

SERVERActual SOURCEactual-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/actual/actual-payees-merge.md

WHAT IT DOES

What actual_payees_merge does on Actual

AI agents use actual_payees_merge 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.

RISK

Why actual_payees_merge is rated Medium

Modifies payee data by merging records; reversible through undo or separate merge operation.

From the tool's definition Merge one or more payees into a target payee. Consolidates duplicate payees

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs actual_payees_merge 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_payees_merge, this is the rule to start with:

actual_payees_merge Rate-limited

actual_payees_merge 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": {
    "actual_payees_merge": {
      "limits": [
        {
          "counter": "actual_payees_merge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_payees_merge call is checked against it from then on.

FAQ

Questions about actual_payees_merge

What does the actual_payees_merge tool do? +

Merge one or more payees into a target payee. This consolidates duplicate payees by merging. 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.

How do I enforce a policy on actual_payees_merge? +

Register the Actual MCP server in PolicyLayer and add a rule for actual_payees_merge: 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 actual_payees_merge? +

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

Can I rate-limit actual_payees_merge? +

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

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

actual_payees_merge 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.

KEEP EXPLORING

More on Actual, and thousands of servers like it.

This server

All 67 Actual tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →