Low Risk

get-payees

Retrieve a list of all payees with their id, name, categoryId and transferAccountId.

How to control get-payees ↓

AI agents call get-payees to retrieve information from Actual without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and lists existing payee data without creating, modifying, or deleting any records. It is a straightforward Read operation with minimal risk since financial data exposure depends on the sensitivity of payee information in the budget context, which is typically low-risk metadata.

From the tool's definition Tool name is 'get-payees' and description states 'Retrieve a list of all payees' — a pure query operation with no side effects.

Documented attack patterns abuse exactly the kind of access get-payees 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 get-payees:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-payees": {}
  }
}

get-payees is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-payees tool do? +

Retrieve a list of all payees with their id, name, categoryId and transferAccountId. It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-payees? +

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

get-payees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-payees? +

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

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

get-payees 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.