Delete an XRP Ledger account and send remaining XRP to a destination account
AI agents call delete-account to permanently remove resources in Xrpl mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a ledger account and transfers its assets. Deletion cannot be undone, making it Destructive rather than merely Write. The critical severity reflects the high blast radius: an AI agent misuse could permanently destroy user accounts and liquidate funds to attacker-controlled addresses. This is among the most damaging operations possible on a blockchain platform.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an XRP Ledger account' which irreversibly removes the account.
Documented attack patterns abuse exactly the kind of access delete-account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xrpl mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-account:
{
"version": "1",
"default": "deny",
"hide": [
"delete-account"
]
} delete-account disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an XRP Ledger account and send remaining XRP to a destination account. It is categorised as a Destructive tool in the Xrpl mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xrpl MCP server in PolicyLayer and add a rule for delete-account: 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 Xrpl mcp. Nothing to install.
delete-account 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-account 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-account. 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-account is provided by the Xrpl MCP server (romthpt/mcp-xrpl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xrpl mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
71 Xrpl mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.