Critical Risk →

permissioned-domain-delete

Delete a Permissioned Domain from the XRP Ledger. Only the domain owner can delete a domain.

How to control permissioned-domain-delete ↓

What permissioned-domain-delete does on Xrpl mcp

AI agents call permissioned-domain-delete 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.

Critical Risk

Why permissioned-domain-delete needs a policy

This tool performs irreversible deletion of a Permissioned Domain object from the ledger. While access control is mentioned (only domain owner can delete), the operation itself is destructive in nature—once deleted, the domain configuration is removed and cannot be undone without recreating it separately.

From the tool's definition The tool description explicitly states 'Delete a Permissioned Domain' and uses the clear destructive verb 'delete'. The action removes data from the XRP Ledger that cannot be recovered.

Documented attack patterns abuse exactly the kind of access permissioned-domain-delete gives an agent:

How to control permissioned-domain-delete

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 permissioned-domain-delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "permissioned-domain-delete"
  ]
}

permissioned-domain-delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Xrpl mcp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about permissioned-domain-delete

What does the permissioned-domain-delete tool do? +

Delete a Permissioned Domain from the XRP Ledger. Only the domain owner can delete a domain. 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.

How do I enforce a policy on permissioned-domain-delete? +

Register the Xrpl MCP server in PolicyLayer and add a rule for permissioned-domain-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 mcp. Nothing to install.

What risk level is permissioned-domain-delete? +

permissioned-domain-delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit permissioned-domain-delete? +

Yes. Add a rate_limit block to the permissioned-domain-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.

How do I block permissioned-domain-delete completely? +

Set action: deny in the PolicyLayer policy for permissioned-domain-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.

What MCP server provides permissioned-domain-delete? +

permissioned-domain-delete 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.

Enforce policy on every Xrpl mcp tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.