resolve_address

SERVERXRPName SOURCE@xrpname/xrpname-mcp

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/resolve-address.md

WHAT IT DOES

What resolve_address does on XRPName

AI agents use resolve_address to create or update resources in XRPName, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XRPName environment.

Parameter	Type	Required	Description
`limit`	integer	—	Maximum number of domains to return (cap 200).
`address`	string	Yes	XRPL classic address, e.g. "rLhi87eXFZNueP4Kg1jUuHmm7pWZBoT3Yn".
`include_history`	boolean	—	If true, include per-domain nftoken_id and mint date.

Parameters from the server's own tool schema.

RISK

Why resolve_address is rated Medium

An AI agent can call resolve_address faster than any human can review: one bad instruction and it creates or modifies resources in XRPName by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_address Rate-limited

resolve_address stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_address": {
      "limits": [
        {
          "counter": "resolve_address_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XRPName, apply this rule, and every resolve_address call is checked against it from then on.

FAQ

Questions about resolve_address

What does the resolve_address tool do? +

Reverse resolution: given an XRPL address, return its primary XRPName (if set) and the full list of names owned by the wallet. Use when the user says "who owns [address]?", "look up this wallet", or "what names does [address] have?", or when chained with get_domain_profile to explore a wallet. Returns found:false if the address owns no XRPName. It is categorised as a Write tool in the XRPName MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does resolve_address accept? +

resolve_address accepts 3 parameters: limit, address, include_history. Required: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_address? +

Register the XRPName MCP server in PolicyLayer and add a rule for resolve_address: 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.

What risk level is resolve_address? +

resolve_address is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_address? +

Yes. Add a rate_limit block to the resolve_address 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 resolve_address completely? +

Set action: deny in the PolicyLayer policy for resolve_address. 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 resolve_address? +

resolve_address 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.

KEEP EXPLORING

More on XRPName, and thousands of servers like it.

This server

All 10 XRPName tools →

Across the catalogue

resolve_projects on ACE-MCP →resolve_circuit on 0gzk → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →