Reject a pending transaction, preventing it from being signed or submitted.
AI agents call reject-transaction to permanently remove resources in Xrpl mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rejecting a pending transaction is an irreversible action that permanently prevents the transaction from being processed. Unlike a cancellation that might allow retry, rejection definitively blocks the transaction from being signed or submitted, making it a destructive/irreversible operation.
From the tool's definition Reject a pending transaction, preventing it from being signed or submitted.
Documented attack patterns abuse exactly the kind of access reject-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 reject-transaction:
{
"version": "1",
"default": "deny",
"hide": [
"reject-transaction"
]
} reject-transaction disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Reject a pending transaction, preventing it from being signed or submitted. It is categorised as a Destructive tool in the Xrpl mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xrpl MCP server in PolicyLayer and add a rule for reject-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.
reject-transaction is a Destructive 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 reject-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 reject-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.
reject-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.