list-wallets

List all registered wallets in the custody system, showing their names, addresses, and types.

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/romthpt-mcp-xrpl/list-wallets.md

WHAT IT DOES

What list-wallets does on Xrpl mcp

AI agents call list-wallets to retrieve information from Xrpl mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list-wallets is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list-wallets 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 list-wallets, this is the rule to start with:

list-wallets Allowed

list-wallets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list-wallets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every list-wallets call is checked against it from then on.

FAQ

Questions about list-wallets

What does the list-wallets tool do? +

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.

How do I enforce a policy on list-wallets? +

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.

What risk level is list-wallets? +

list-wallets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list-wallets? +

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.

How do I block list-wallets completely? +

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.

What MCP server provides list-wallets? +

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.

KEEP EXPLORING

More on Xrpl, and thousands of servers like it.

This server

All 71 Xrpl tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →