Get month-by-month income, expense, net amount, and transaction count for a month range.
AI agents call whooing_monthly_summary 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 aggregates existing financial data without modification, deletion, or execution of external operations. It presents historical summaries rather than sensitive transaction details. While it accesses financial information, it does not move money, create obligations, or permit side effects.
From the tool's definition Tool description states 'Get month-by-month income, expense, net amount, and transaction count' — purely retrieval of aggregated financial summary data. Server description emphasizes 'read-only access' and 'query and analyze their financial history.'
Attacks that exploit this kind of access
Get month-by-month income, expense, net amount, and transaction count for a month range. 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_monthly_summary: 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_monthly_summary 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_monthly_summary 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_monthly_summary. 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_monthly_summary 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 →