List all registered wallets in the custody system, showing their names, addresses, and types.
AI agents call list-wallets 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 wallet metadata (names, addresses, types) from a custody system without creating, modifying, deleting, or executing operations. However, severity is elevated to medium rather than low because wallet addresses and enumeration of custody accounts could enable reconnaissance for targeted attacks or social engineering, particularly in a financial context (XRP Ledger).
From the tool's definition Tool name 'list-wallets' and description 'List all registered wallets in the custody system, showing their names, addresses, and types' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list-wallets 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-wallets:
{
"version": "1",
"default": "deny",
"tools": {
"list-wallets": {}
}
}list-wallets 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 registered wallets in the custody system, showing their names, addresses, and types. 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-wallets: 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-wallets 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-wallets 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-wallets. 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-wallets 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.