check_domains
Check 1 to 25 XRPL domains for registration status and cost. Use for questions like "is <name>.xrp taken?", "how much does <name>.xrp cost?", "who owns <name>.xrp?", or to verify availability before registering. Accepts .xrp, .xrpl, .xrpfi, .rlusd TLDs (defaults to .xrp when omitted). Returns ava...
This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/check-domains.md
What check_domains does on XRPName
AI agents call check_domains 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 |
|---|---|---|---|
domains | array | Yes | List of domains to check. Each may include or omit the TLD; defaults to .xrp. |
Parameters from the server's own tool schema.
Why check_domains is rated Low
Tool retrieves domain registration status and pricing data without modifying state or executing operations.
From the tool's definition Check availability, price, owner address, profile metadata; read-only queries.
Attacks that exploit this kind of access
The rule that runs check_domains 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 check_domains, this is the rule to start with:
check_domains 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 check_domains call is checked against it from then on.
Questions about check_domains
Check 1 to 25 XRPL domains for registration status and cost. Use for questions like "is <name>.xrp taken?", "how much does <name>.xrp cost?", "who owns <name>.xrp?", or to verify availability before registering. Accepts .xrp, .xrpl, .xrpfi, .rlusd TLDs (defaults to .xrp when omitted). Returns availability, price in XRP and RLUSD, owner address, profile metadata if registered, and a web URL for the user to register if available. Also returns invalid_domains for inputs that fail validation. It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.
check_domains accepts 1 parameter: domains. Required: domains. 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 check_domains: 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.
check_domains 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 check_domains 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 check_domains. 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.
check_domains 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