Approve a pending transaction, signing and submitting it to the XRP Ledger. This is a destructive action that sends a real transaction.
AI agents use approve-transaction 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 approves, signs, and submits a real transaction to the XRP Ledger. Transactions on the XRP Ledger can involve transferring XRP or tokens, committing financial obligations, or triggering irreversible on-chain operations.
From the tool's definition 'signing and submitting it to the XRP Ledger' and 'sends a real transaction' — approves and submits a pending financial transaction on the XRP Ledger
Documented attack patterns abuse exactly the kind of access approve-transaction 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 approve-transaction:
{
"version": "1",
"default": "deny",
"tools": {
"approve-transaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to approve-transaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Approve a pending transaction, signing and submitting it to the XRP Ledger. This is a destructive action that sends a real transaction. 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 approve-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. Nothing to install.
approve-transaction 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 approve-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.
Set action: deny in the PolicyLayer policy for approve-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.
approve-transaction 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.