Permanently delete a wallet and all its data.
AI agents call delete_wallet to permanently remove resources in Money Lover MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes a wallet and all its data. Deletion cannot be undone without a backup restore, making it Destructive rather than Write. The blast radius is high because an AI agent could accidentally or maliciously wipe out a user's entire wallet record, including all transactions and financial history associated with it.
From the tool's definition 'Permanently delete a wallet and all its data' — the description explicitly states irreversible deletion of a wallet and associated data.
Attacks that exploit this kind of access
Permanently delete a wallet and all its data. It is categorised as a Destructive tool in the Money Lover MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Money Lover MCP Server MCP server in PolicyLayer and add a rule for delete_wallet: 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 Money Lover MCP Server. Nothing to install.
delete_wallet 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 delete_wallet 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 delete_wallet. 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.
delete_wallet is provided by the Money Lover MCP Server MCP server (juansebashr/moneylover-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 →