AI agents call search_transactions to retrieve information from MoneyWiz MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search/query operation on financial transaction data. The server explicitly advertises read-only access, and the naming pattern alongside peer tools (which retrieve and analyze data without modification) indicates this is a retrieval operation. No destructive, write, execute, or financial movement capabilities are evident.
From the tool's definition Tool name 'search_transactions' combined with server description stating 'secure, read-only access to MoneyWiz financial data for natural language queries and financial analytics.' All sibling tools (analyze_*, get_*) are clearly Read operations.
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 MoneyWiz 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. It is categorised as a Read tool in the MoneyWiz MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MoneyWiz 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 MoneyWiz 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 MoneyWiz MCP Server MCP server (jcvalerio/moneywiz-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MoneyWiz 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.
15 MoneyWiz MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.