amm-clawback
Clawback assets from an Automated Market Maker (AMM)
This record as markdown: /tools/romthpt-mcp-xrpl/amm-clawback.md
What amm-clawback does on Xrpl mcp
AI agents use amm-clawback to commit financial operations through Xrpl mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why amm-clawback is rated Critical
Clawback is a financial operation that retrieves/reclaims assets from an AMM, directly moving cryptocurrency/tokens. This is a financial transaction on the XRP Ledger that moves funds and cannot be trivially reversed, making it Financial category with critical severity due to potential for misuse (draining assets from AMM positions).
From the tool's definition "Clawback assets from an Automated Market Maker (AMM)" — forcibly reclaims/retrieves financial assets from an AMM pool
Attacks that exploit this kind of access
The rule that runs amm-clawback 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-clawback, this is the rule to start with:
Any call to amm-clawback is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every amm-clawback call is checked against it from then on.
Questions about amm-clawback
Clawback assets from an Automated Market Maker (AMM). It is categorised as a Financial tool in the Xrpl mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Xrpl MCP server in PolicyLayer and add a rule for amm-clawback: 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.
amm-clawback is a Financial 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 amm-clawback 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 amm-clawback. 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.
amm-clawback 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.
More on Xrpl, and thousands of servers like it.
Across the catalogue