This record as markdown: /tools/romthpt-mcp-xrpl/check-cash.md
What check-cash does on Xrpl mcp
AI agents use check-cash to commit financial operations through Xrpl mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why check-cash is rated Critical
Cashing a check is a financial operation that transfers XRP or token funds from one party to another on the XRP Ledger. This constitutes a financial transaction with direct monetary consequences, making it Financial category with critical severity since misuse could result in unauthorized fund transfers on a live blockchain.
From the tool's definition 'Cash a Check to receive funds from it' - this tool moves funds/assets on the XRP Ledger by cashing a check to receive payment
Attacks that exploit this kind of access
The rule that runs check-cash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check-cash, this is the rule to start with:
Any call to check-cash is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every check-cash call is checked against it from then on.
Questions about check-cash
Cash a Check to receive funds from it. 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 check-cash: 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.
check-cash 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 check-cash 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 check-cash. 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.
check-cash 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.
More on Xrpl, and thousands of servers like it.
Across the catalogue