submit_transaction

THE RISK

Critical Risk

Why submit_transaction needs a policy

Submitting a signed transaction to the XRP Ledger is a financial action: it can transfer XRP or tokens, create/cancel offers, modify trust lines, or other ledger-altering operations. Once submitted and validated, transactions are irreversible. This is both Financial and Destructive in nature, and Financial is the highest severity category.

From the tool's definition 'Submit a signed transaction blob to the XRP Ledger' — submitting transactions to the XRP Ledger directly moves XRP or other assets, modifies ledger state, and commits financial operations irreversibly.

Documented attack patterns abuse exactly the kind of access submit_transaction gives an agent:

POLICY

How to control submit_transaction

PolicyLayer is an MCP gateway — it sits between your AI agents and XRPL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_transaction:

policy.json

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

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

Create a free account and register XRPL MCP Server — 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 Server tools

Read get_account_info Get information about an XRP Ledger account. Read get_account_lines Get the trust lines for an XRP Ledger account. Read get_account_nfts Get the NFTs owned by an XRP Ledger account. Read get_account_transactions Get the transaction history for an XRP Ledger account. Read get_book_offers Get the order book offers for a currency pair on the DEX. Read get_server_info Get information about the connected XRP Ledger server. Read get_transaction_info Get information about a specific transaction by its hash.

All 8 XRPL MCP Server 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 Server → 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 submit_transaction

What does the submit_transaction tool do? +

Submit a signed transaction blob to the XRP Ledger. It is categorised as a Financial tool in the XRPL MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on submit_transaction? +

Register the XRPL MCP Server MCP server in PolicyLayer and add a rule for submit_transaction: 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 Server. Nothing to install.

What risk level is submit_transaction? +

submit_transaction 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 submit_transaction? +

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

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

submit_transaction is provided by the XRPL MCP Server MCP server (lgcarrier/xrpl-mcp-server). 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 Server tool call.

Start from XRPL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →