register_domain
Get the link to register a .xrp / .xrpl / .xrpfi / .rlusd domain on xrpdomains.xyz. Registration is completed in the browser — the website handles the order and the user signs in their wallet there (the MCP does NOT build or broadcast the payment). Use when the user says "register X.xrpfi" or "bu...
This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/register-domain.md
What register_domain does on XRPName
AI agents use register_domain 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 |
|---|---|---|---|
domain | string | Yes | The domain to register, e.g. "coolname.xrpfi". |
refcode | string | — | Optional referral code to embed in the registration link. |
Parameters from the server's own tool schema.
Why register_domain is rated Medium
Provides registration link that initiates domain purchase; user completes financial commitment externally via browser wallet.
From the tool's definition Get the link to register .xrp / .xrpl / .xrpfi / .rlusd domain
Attacks that exploit this kind of access
The rule that runs register_domain 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 register_domain, this is the rule to start with:
register_domain 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.
The button opens the PolicyLayer dashboard: create your workspace, connect XRPName, apply this rule, and every register_domain call is checked against it from then on.
Questions about register_domain
Get the link to register a .xrp / .xrpl / .xrpfi / .rlusd domain on xrpdomains.xyz. Registration is completed in the browser — the website handles the order and the user signs in their wallet there (the MCP does NOT build or broadcast the payment). Use when the user says "register X.xrpfi" or "buy X.xrp". Pass refcode if a referral applies. 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.
register_domain accepts 2 parameters: domain, refcode. Required: domain. 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 register_domain: 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.
register_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_domain 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 register_domain. 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.
register_domain 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