Search transactions with query, account, amount, and date filters. Prefer this for natural-language find/search requests.
AI agents call whooing_search_entries to retrieve information from Whooing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters transaction data without creating, modifying, or deleting records. It is a straightforward query operation on financial data with no side effects, placing it squarely in the Read category. The blast radius of misuse is low since the agent cannot alter financial records or execute arbitrary operations—only retrieve existing information that the user already has access to.
From the tool's definition Tool description states 'Search transactions' with filters; server description emphasizes 'read-only access' and 'query and analyze' capabilities. The tool name contains 'search' and description contains no modification, deletion, or execution language.
Attacks that exploit this kind of access
Search transactions with query, account, amount, and date filters. Prefer this for natural-language find/search requests. It is categorised as a Read tool in the Whooing MCP MCP Server, which means it retrieves data without modifying state.
Register the Whooing MCP server in PolicyLayer and add a rule for whooing_search_entries: 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 Whooing MCP. Nothing to install.
whooing_search_entries 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 whooing_search_entries 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 whooing_search_entries. 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.
whooing_search_entries is provided by the Whooing MCP server (jmjeong/whooing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →