Delete a transaction entry from Whooing.
AI agents call whooing_delete_entry to permanently remove resources in Whooing MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes transaction records from a personal finance system. Deletion of financial entries cannot be undone and destroys historical data that may be needed for tax, audit, or reconciliation purposes. While the server itself provides read-only access, this specific tool performs a destructive operation.
From the tool's definition Tool name is 'whooing_delete_entry' with description 'Delete a transaction entry from Whooing.' The verb 'delete' combined with 'entry' indicates irreversible removal of financial transaction data.
Attacks that exploit this kind of access
Delete a transaction entry from Whooing. It is categorised as a Destructive tool in the Whooing MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Whooing MCP server in PolicyLayer and add a rule for whooing_delete_entry: 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_delete_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the whooing_delete_entry 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_delete_entry. 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_delete_entry 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 →