List frequently used transactions (templates for quick entry).
AI agents call whooing_frequent_items 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.
The tool performs a simple query/list operation to retrieve frequently used transaction templates. It has no side effects, does not modify, delete, or execute any operations. It is purely informational retrieval of historical transaction patterns for reference purposes. Blast radius is minimal—misuse would only expose transaction template data that the user already owns.
From the tool's definition Tool is described as 'List frequently used transactions' with no modification or deletion capability. The server description explicitly states it 'Enables read-only access' to personal finance data.
Attacks that exploit this kind of access
List frequently used transactions (templates for quick entry). 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_frequent_items: 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_frequent_items 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_frequent_items 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_frequent_items. 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_frequent_items 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 →