Summarize activity for one account in a date range, including totals, frequent items, and recent matching entries.
AI agents call whooing_account_activity 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 summarizes existing financial account data without modification. While it accesses sensitive personal finance information (which elevates severity to medium due to privacy and data exposure risks), it performs no write, destructive, execute, or financial transaction operations. The primary risk is unauthorized information disclosure rather than operational impact.
From the tool's definition Tool description states it 'Summarize[s] activity for one account in a date range' with 'totals, frequent items, and recent matching entries' — purely retrieval and analysis operations. Server description confirms 'read-only access' to financial data.
Attacks that exploit this kind of access
Summarize activity for one account in a date range, including totals, frequent items, and recent matching entries. 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_account_activity: 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_account_activity 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_account_activity 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_account_activity. 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_account_activity 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 →