actual_payee_rules_get
Get all payee rules associated with a specific payee. Returns PayeeRule objects that show how transactions with this payee are automatically processed (conditions and actions).
This record as markdown: /tools/actual/actual-payee-rules-get.md
What actual_payee_rules_get does on Actual
AI agents call actual_payee_rules_get to retrieve information from Actual without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why actual_payee_rules_get is rated Low
This tool retrieves and displays existing payee rule configurations without modifying, executing, or deleting them. Even though the rules themselves describe automated transaction processing, this tool only reads their definitions. The blast radius of misuse is minimal — an attacker can only learn what rules exist, not alter system behavior or financial data. Classified as Read with low severity.
From the tool's definition Tool description states 'Get all payee rules' — a retrieval operation that 'Returns PayeeRule objects' with no mention of modification, deletion, or execution of those rules. The verb 'Get' indicates read-only querying of configuration data.
Attacks that exploit this kind of access
The rule that runs actual_payee_rules_get 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_payee_rules_get, this is the rule to start with:
actual_payee_rules_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_payee_rules_get call is checked against it from then on.
Questions about actual_payee_rules_get
Get all payee rules associated with a specific payee. Returns PayeeRule objects that show how transactions with this payee are automatically processed (conditions and actions). It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.
Register the Actual MCP server in PolicyLayer and add a rule for actual_payee_rules_get: 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.
actual_payee_rules_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the actual_payee_rules_get 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 actual_payee_rules_get. 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.
actual_payee_rules_get 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.
More on Actual, and thousands of servers like it.
This server
Across the catalogue