Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting.
AI agents call did_prepare_delete to permanently remove resources in Xrpl Identity — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
DIDDelete operations remove identity credentials from the XRP Ledger permanently. While the tool itself only prepares the transaction (does not execute it), the underlying operation is destructive. Misuse could delete critical identity documents for an account. This is more severe than Write (reversible modifications) because DID deletion is irreversible.
From the tool's definition Tool prepares a DIDDelete transaction that irreversibly deletes an account DID (XLS-40 identity document). The word 'Delete' combined with DID context indicates permanent removal of identity data that cannot be undone.
Attacks that exploit this kind of access
Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting. It is categorised as a Destructive tool in the Xrpl Identity MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xrpl Identity MCP server in PolicyLayer and add a rule for did_prepare_delete: 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 Identity. Nothing to install.
did_prepare_delete 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 did_prepare_delete 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 did_prepare_delete. 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.
did_prepare_delete is provided by the Xrpl Identity MCP server (jarod-vyent/xrpl-identity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
did_prepare_delete is one line of Xrpl Identity's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →