Get the full list of accounts (assets, liabilities, income, expenses, capital)
AI agents call whooing_accounts 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 account information without creating, modifying, or deleting any data. It is purely informational and read-only in nature. The blast radius of misuse is minimal—an attacker could view account structure but cannot alter financial records or move money. Low severity because financial data exposure is present but this tool itself does not enable financial transactions or destructive actions.
From the tool's definition Tool name 'whooing_accounts' and description 'Get the full list of accounts' indicate a retrieval operation. Server description emphasizes 'read-only access' and 'query and analyze' without modification.
Attacks that exploit this kind of access
Get the full list of accounts (assets, liabilities, income, expenses, capital). 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_accounts: 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_accounts 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_accounts 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_accounts. 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_accounts 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 →