List all transactions that are pending approval. These are transactions that have been prepared but not yet signed and submitted.
AI agents call list-pending-transactions to retrieve information from Xrpl mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays pending transaction data without creating, modifying, executing, or deleting anything. It has no side effects and poses minimal risk even if misused by an AI agent, as it only exposes already-prepared but unsigned transaction metadata.
From the tool's definition Tool name includes 'list' and description states it 'List[s] all transactions that are pending approval' with no modifications or submissions—purely a query operation.
Documented attack patterns abuse exactly the kind of access list-pending-transactions 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 list-pending-transactions:
{
"version": "1",
"default": "deny",
"tools": {
"list-pending-transactions": {}
}
}list-pending-transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all transactions that are pending approval. These are transactions that have been prepared but not yet signed and submitted. It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.
Register the Xrpl MCP server in PolicyLayer and add a rule for list-pending-transactions: 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.
list-pending-transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-pending-transactions 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 list-pending-transactions. 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.
list-pending-transactions 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.