transfer-token

THE RISK

Critical Risk

Why transfer-token needs a policy

This tool moves money or financial assets (tokens on XRP Ledger) from one address to another. Tokens on blockchain networks represent real financial value. An AI agent misusing this tool could transfer user funds to arbitrary addresses, resulting in irreversible financial loss. The combination of the sibling tools (batch-payment, approve-transaction, etc.) confirms this server's financial transaction capabilities.

From the tool's definition Tool name is 'transfer-token' and description states 'Transfer tokens between addresses'. Within the XRP Ledger context (a blockchain with real monetary value), transferring tokens directly moves financial assets between accounts.

Documented attack patterns abuse exactly the kind of access transfer-token gives an agent:

POLICY

How to control transfer-token

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-token:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer-token": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to transfer-token is blocked until a human approves it. The rest of the server keeps working.

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

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Xrpl mcp tools

Financial amm-deposit Deposit assets into an existing Automated Market Maker (AMM) on the XRP Ledger Financial transfer-xrp Transfer XRP between accounts using the connected wallet or a named wallet Financial check-cash Cash a Check to receive funds from it Financial amm-bid Place a bid on an Automated Market Maker Financial amm-clawback Clawback assets from an Automated Market Maker (AMM) Financial amm-create Create a new Automated Market Maker (AMM) on the XRP Ledger Financial approve-transaction Approve a pending transaction, signing and submitting it to the XRP Ledger. This is a dest Financial batch-payment Submit a batch of payment transactions. This is a convenience wrapper around batch-submit

All 71 Xrpl mcp tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in Xrpl mcp → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about transfer-token

What does the transfer-token tool do? +

Transfer tokens between addresses. 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.

How do I enforce a policy on transfer-token? +

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

transfer-token is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer-token? +

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

Set action: deny in the PolicyLayer policy for transfer-token. 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 transfer-token? +

transfer-token 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.

CHECK YOUR STACK →