// SCAN REPORT

XRPName

10 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 1 Oct 2026

3 can modify or destroy data

7 read-only

10 tools total

Community server · catalogue entry checked 01/10/2026 · full schemas captured for 10 of 10 tools

How to control XRPName ↓

TOOL MAP

What XRPName exposes to your agents

Read (7) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What XRPName costs in tokens

1,908 tokens of tool definitions, loaded on every request

1.0% of a 200k context window

266 heaviest tool: get_portfolio

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous XRPName tools

Write · Medium register_domain Provides registration link that initiates domain purchase; user completes financial commitment externally via browser wallet. Write · Medium resolve_address 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 Write · Medium set_primary_domain Get the link to set a domain as your wallet's primary (the name shown by default for your address). Setting primary is completed in the brow

3 of XRPName's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control XRPName

PolicyLayer is an MCP gateway — it sits between your AI agents and XRPName, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "register_domain": {
    "limits": [
      {
        "counter": "register_domain_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_domains": {
    "limits": [
      {
        "counter": "check_domains_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register XRPName — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON XRPNAME →

Instant setup, no code required.

FULL CATALOGUE

All 10 XRPName tools

WRITE 3 tools

Write register_domain Get the link to register a .xrp / .xrpl / .xrpfi / .rlusd domain on xrpdomains.xyz. Registration is completed Write resolve_address Reverse resolution: given an XRPL address, return its primary XRPName (if set) and the full list of names owne Write set_primary_domain Get the link to set a domain as your wallet's primary (the name shown by default for your address). Setting pr

READ 7 tools

Read check_domains Check 1 to 25 XRPL domains for registration status and cost. Use for questions like "is <name>.xrp taken?", "h Read check_order_status Check the backend order status for a domain you tried to register on xrpdomains.xyz. Returns whether payment l Read check_tx_status Check the validation status of an XRPL transaction by hash. Use after send_signed_tx to confirm whether the tr Read get_domain_profile Get the full public profile of a single XRPL domain — owner, NFT token ID, metadata, avatar, fullname, descrip Read get_pending_offers Get all pending XRPL domain operations for a wallet — incoming offers (someone offered the wallet a domain), o Read get_portfolio List all XRPL domains owned by a wallet address. Use when the user asks "what domains do I own?", "show me my Read recommend_domain Get AI-recommended domain suggestions for a keyword or theme (e.g. "tom", "crypto", "defi"). Returns creative

FAQ

Questions about XRPName

How do I prevent bulk modifications through XRPName? +

The XRPName server has 3 write tools including register_domain, resolve_address, set_primary_domain. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach XRPName.

How many tools does the XRPName MCP server expose? +

10 tools across 2 categories: Read, Write. 7 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on XRPName? +

Register the XRPName MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every XRPName tool call.

Deterministic rules across all 10 XRPName tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON XRPNAME →

Instant setup, no code required.

10 XRPName tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from XRPName's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →