Critical Risk →

payment-channel-fund

Add additional XRP to an existing Payment Channel

How to control payment-channel-fund ↓

What payment-channel-fund does on Xrpl mcp

AI agents use payment-channel-fund to commit financial operations through Xrpl mcp — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why payment-channel-fund needs a policy

This tool moves XRP (a financial asset) by funding a payment channel on the XRP Ledger. Committing cryptocurrency to a payment channel is a financial operation that locks real value. Misuse could result in unintended transfer or locking of funds.

From the tool's definition Add additional XRP to an existing Payment Channel

Documented attack patterns abuse exactly the kind of access payment-channel-fund gives an agent:

How to control payment-channel-fund

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 payment-channel-fund:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "payment-channel-fund": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to payment-channel-fund is blocked until a human approves it. 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.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about payment-channel-fund

What does the payment-channel-fund tool do? +

Add additional XRP to an existing Payment Channel. 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 payment-channel-fund? +

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

payment-channel-fund 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 payment-channel-fund? +

Yes. Add a rate_limit block to the payment-channel-fund 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 payment-channel-fund completely? +

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

payment-channel-fund 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.