get_domain_profile

SERVERXRPName SOURCE@xrpname/xrpname-mcp

Low RISK CLASS

Category Read

Parameters 21 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/get-domain-profile.md

WHAT IT DOES

What get_domain_profile does on XRPName

AI agents call get_domain_profile 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
`domain`	string	Yes	Domain to look up, e.g. "alice.xrp"
`include_history`	boolean	—	Include the on-chain ownership timeline (transfers, marketplace sales).

Parameters from the server's own tool schema.

RISK

Why get_domain_profile is rated Low

Tool retrieves public profile data without modifying or executing operations; read-only information query.

From the tool's definition Get the full public profile of a single XRPL domain — owner, NFT token ID, metadata, avatar, fullname, description, social handles, linked chain addresses, and optionally the on-chain ownership history.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_domain_profile Allowed

get_domain_profile 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": {
    "get_domain_profile": {}
  }
}

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 get_domain_profile call is checked against it from then on.

FAQ

Questions about get_domain_profile

What does the get_domain_profile tool do? +

Get the full public profile of a single XRPL domain — owner, NFT token ID, metadata, avatar, fullname, description, social handles, linked chain addresses, and optionally the on-chain ownership history (pass include_history=true). Use when the user asks "show me X.xrp", "what does X.xrp link to?", "who owns X.xrp?", or "show me the history of X.xrp". Returns null fields gracefully if no profile is set. It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.

What parameters does get_domain_profile accept? +

get_domain_profile accepts 2 parameters: domain, include_history. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_domain_profile? +

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

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

Can I rate-limit get_domain_profile? +

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

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

get_domain_profile 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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