Search transactions by text in payee, memo, or category fields
AI agents call search_transactions to retrieve information from Quicken MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation on financial transaction data. While the underlying data is financial in nature, the tool itself does not move money, create obligations, or modify state—it only retrieves and filters existing transaction records. The severity is low because misuse would result in unauthorized information access rather than direct financial harm or irreversible data loss.
From the tool's definition Tool name 'search_transactions' and description 'Search transactions by text in payee, memo, or category fields' indicate a query operation that retrieves data without modifying it.
Documented attack patterns abuse exactly the kind of access search_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quicken MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"search_transactions": {}
}
}search_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search transactions by text in payee, memo, or category fields. It is categorised as a Read tool in the Quicken MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Quicken MCP Server MCP server in PolicyLayer and add a rule for search_transactions: 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 Quicken MCP Server. Nothing to install.
search_transactions 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 search_transactions 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 search_transactions. 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.
search_transactions is provided by the Quicken MCP Server MCP server (sgoley/quicken-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quicken MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Quicken MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.