get_portfolio
List all XRPL domains owned by a wallet address. Use when the user asks "what domains do I own?", "show me my domains", or wants to see another wallet's holdings. Returns each domain with its TLD, length, primary flag, subname flag, and quick-action URLs. (nftoken_id, image, and mint time are not...
This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/get-portfolio.md
What get_portfolio does on XRPName
AI agents call get_portfolio to retrieve information from XRPName without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | Sort order. "recent" keeps the backend order. |
limit | integer | — | Max domains to return. |
address | string | Yes | XRPL r... address whose domains to list. |
filter_tld | string | — | Filter by TLD, e.g. ".xrp", ".xrpfi", ".rlusd", or "all". |
Parameters from the server's own tool schema.
Why get_portfolio is rated Low
Retrieves and lists domain ownership data without modification or side effects.
From the tool's definition List all XRPL domains owned by a wallet address. Returns each domain.
Attacks that exploit this kind of access
The rule that runs get_portfolio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and XRPName, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_portfolio, this is the rule to start with:
get_portfolio is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect XRPName, apply this rule, and every get_portfolio call is checked against it from then on.
Questions about get_portfolio
List all XRPL domains owned by a wallet address. Use when the user asks "what domains do I own?", "show me my domains", or wants to see another wallet's holdings. Returns each domain with its TLD, length, primary flag, subname flag, and quick-action URLs. (nftoken_id, image, and mint time are not included here — use get_domain_profile for one domain.) Requires an XRPL r... address. It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.
get_portfolio accepts 4 parameters: sort, limit, address, filter_tld. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the XRPName MCP server in PolicyLayer and add a rule for get_portfolio: 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 XRPName. Nothing to install.
get_portfolio 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 get_portfolio 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 get_portfolio. 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.
get_portfolio is provided by the XRPName MCP server (@xrpname/xrpname-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on XRPName, and thousands of servers like it.
This server
Across the catalogue