actual_transactions_search_by_month
Search transactions for a specific month. Returns all transactions matching the month and optional filters (account, category, payee, amount range). Efficiently queries by date range.
This record as markdown: /tools/actual/actual-transactions-search-by-month.md
What actual_transactions_search_by_month does on Actual
AI agents call actual_transactions_search_by_month 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_month is rated Low
This tool retrieves financial transaction data based on specified filters. While it operates on sensitive financial information, it performs only a read operation without the ability to modify, delete, or execute transactions. The 'search' and 'query' language confirms it is a retrieval function.
From the tool's definition Tool description states 'Search transactions' and 'queries by date range' — core retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs actual_transactions_search_by_month 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_month, this is the rule to start with:
actual_transactions_search_by_month 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_month call is checked against it from then on.
Questions about actual_transactions_search_by_month
Search transactions for a specific month. Returns all transactions matching the month and optional filters (account, category, payee, amount range). Efficiently queries by date range. 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_month: 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_month 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_month 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_month. 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_month 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