amm-delete

Delete an Automated Market Maker (AMM) from the XRP Ledger

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/romthpt-mcp-xrpl/amm-delete.md

WHAT IT DOES

What amm-delete does on Xrpl mcp

AI agents call amm-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.

RISK

Why amm-delete is rated Critical

Deleting an AMM from the XRP Ledger is a destructive operation that permanently removes a financial instrument and its associated state. This action cannot be reversed and represents a loss of the AMM resource. While not directly moving funds (Financial), it irreversibly destroys data/objects on the ledger, making Destructive the appropriate category.

From the tool's definition Tool name contains 'delete' and description states 'Delete an Automated Market Maker (AMM) from the XRP Ledger' — this is an irreversible removal of a ledger object that cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs amm-delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amm-delete, this is the rule to start with:

amm-delete Hidden

amm-delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "amm-delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every amm-delete call is checked against it from then on.

FAQ

Questions about amm-delete

What does the amm-delete tool do? +

Delete an Automated Market Maker (AMM) from the XRP Ledger. 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 amm-delete? +

Register the Xrpl MCP server in PolicyLayer and add a rule for amm-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 amm-delete? +

amm-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 amm-delete? +

Yes. Add a rate_limit block to the amm-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 amm-delete completely? +

Set action: deny in the PolicyLayer policy for amm-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 amm-delete? +

amm-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.

KEEP EXPLORING

More on Xrpl, and thousands of servers like it.

This server

All 71 Xrpl tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →