recommend_domain

Get AI-recommended domain suggestions for a keyword or theme (e.g. "tom", "crypto", "defi"). Returns creative name + TLD combos with a category, each cross-checked for availability, priced, and given a register link. Use when a user asks "suggest names", "find me a domain about X", or "give me so...

SERVERXRPName SOURCE@xrpname/xrpname-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

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

WHAT IT DOES

What recommend_domain does on XRPName

AI agents call recommend_domain 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
`tlds`	array	—	TLDs to include (without dots), e.g. ["xrp","xrpfi"]. Omit for all.
`limit`	integer	—	How many suggestions to return.
`query`	string	Yes	Keyword or theme to base suggestions on, e.g. "tom" or "crypto".

Parameters from the server's own tool schema.

RISK

Why recommend_domain is rated Low

Tool queries availability and pricing data, returning suggestions without creating or modifying any domains.

From the tool's definition Get AI-recommended domain suggestions, availability checked, priced, returns register link

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recommend_domain Allowed

recommend_domain is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recommend_domain": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about recommend_domain

What does the recommend_domain tool do? +

What parameters does recommend_domain accept? +

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

How do I enforce a policy on recommend_domain? +

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

What risk level is recommend_domain? +

recommend_domain is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit recommend_domain? +

Yes. Add a rate_limit block to the recommend_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.

How do I block recommend_domain completely? +

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

What MCP server provides recommend_domain? +

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

KEEP EXPLORING

More on XRPName, and thousands of servers like it.

This server

All 10 XRPName tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →