Get budget status (expenses) for a date range. Dates use YYYYMM (month) format.
AI agents call whooing_budget 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 queries and retrieves budget expense information within specified date ranges. It performs no writes, deletions, code execution, or financial transactions. The read-only nature and query-only purpose place it firmly in the Read category. Severity is low because retrieving personal finance summaries poses minimal risk even if misused by an AI agent—it cannot alter financial state or commit obligations.
From the tool's definition Tool description states 'Get budget status (expenses) for a date range' — purely a retrieval operation with no side effects. Server description confirms 'read-only access' to financial data.
Attacks that exploit this kind of access
Get budget status (expenses) for a date range. Dates use YYYYMM (month) format. 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_budget: 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_budget 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_budget 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_budget. 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_budget 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 →