actual_transactions_search_by_amount
Search transactions by amount. Supports two modes: (1) Signed amount range using minAmount/maxAmount (expenses are negative, e.g., -5000 for -$50), or (2) Absolute value using absoluteAmount to find any transaction with that magnitude regardless of sign (e.g., absoluteAmount=5000 matches both +$5...
This record as markdown: /tools/actual/actual-transactions-search-by-amount.md
What actual_transactions_search_by_amount does on Actual
AI agents call actual_transactions_search_by_amount 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_transactions_search_by_amount is rated Low
This tool retrieves/queries existing transaction data based on amount criteria. It has no side effects—it only searches and returns results without creating, modifying, deleting, or executing operations. This is a classic Read operation. Severity is low because the tool only accesses financial data already owned by the user, with no destructive or high-impact capability.
From the tool's definition Tool name contains 'search' and description states 'Search transactions by amount' with query parameters (minAmount/maxAmount/absoluteAmount). No modification, deletion, or execution of commands described.
Attacks that exploit this kind of access
The rule that runs actual_transactions_search_by_amount 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_transactions_search_by_amount, this is the rule to start with:
actual_transactions_search_by_amount 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_transactions_search_by_amount call is checked against it from then on.
Questions about actual_transactions_search_by_amount
Search transactions by amount. Supports two modes: (1) Signed amount range using minAmount/maxAmount (expenses are negative, e.g., -5000 for -$50), or (2) Absolute value using absoluteAmount to find any transaction with that magnitude regardless of sign (e.g., absoluteAmount=5000 matches both +$50 income and -$50 expense). When user says. 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_transactions_search_by_amount: 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_transactions_search_by_amount 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_transactions_search_by_amount 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_transactions_search_by_amount. 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_transactions_search_by_amount 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