Transfer XRP between accounts using the connected wallet or a named wallet
AI agents use transfer-xrp to commit financial operations through Xrpl mcp — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves money (XRP cryptocurrency) between accounts. Financial category applies due to the irreversible transfer of value. Severity is critical because an AI agent misusing this tool could drain accounts or commit unauthorized transfers of significant sums. High confidence based on explicit financial operation described.
From the tool's definition Tool name 'transfer-xrp' and description states it 'Transfer[s] XRP between accounts', which moves cryptocurrency between parties, constituting a financial transaction with direct monetary impact.
Documented attack patterns abuse exactly the kind of access transfer-xrp 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 transfer-xrp:
{
"version": "1",
"default": "deny",
"tools": {
"transfer-xrp": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer-xrp is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer XRP between accounts using the connected wallet or a named wallet. 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 transfer-xrp: 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.
transfer-xrp 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 transfer-xrp 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 transfer-xrp. 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.
transfer-xrp 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.