domain_fetch_domain_rdap
Fetch domain registration details via IANA RDAP (the modern structured replacement for WHOIS). Read-only. No side effects. Idempotent. domain: Domain name without protocol e.g. example.com not https://example.com. Required. Returns registrar, registration date, expiry date, nameservers, and regis...
This record as markdown: /tools/dev-7bd0-mcp-server/domain-fetch-domain-rdap.md
What domain_fetch_domain_rdap does on DataNexus MCP
AI agents call domain_fetch_domain_rdap to retrieve information from DataNexus MCP 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 | — | Domain without protocol e.g. example.com. Required. |
Parameters from the server's own tool schema.
Why domain_fetch_domain_rdap is rated Low
This tool retrieves publicly available domain registration metadata from authoritative sources (IANA RDAP). It performs no writes, deletes, executes code, or financial operations. The read-only designation and idempotent nature confirm it belongs in the Read category. Severity is low because domain registration details are publicly available and querying them poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states: 'Read-only. No side effects. Idempotent.' It fetches domain registration details via IANA RDAP (publicly available registry data).
Attacks that exploit this kind of access
The rule that runs domain_fetch_domain_rdap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_fetch_domain_rdap, this is the rule to start with:
domain_fetch_domain_rdap 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 DataNexus MCP, apply this rule, and every domain_fetch_domain_rdap call is checked against it from then on.
Questions about domain_fetch_domain_rdap
Fetch domain registration details via IANA RDAP (the modern structured replacement for WHOIS). Read-only. No side effects. Idempotent. domain: Domain name without protocol e.g. example.com not https://example.com. Required. Returns registrar, registration date, expiry date, nameservers, and registrant info where publicly available. Use this when you need registration metadata. Use domain_fetch_ssl_certificate_chain instead when you need certificate history. Use domain_fetch_dns_records instead when you need live DNS resolution. Verified source: IANA RDAP. 4-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="domain_fetch_domain_rdap", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
domain_fetch_domain_rdap accepts 1 parameter: domain. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for domain_fetch_domain_rdap: 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 DataNexus MCP. Nothing to install.
domain_fetch_domain_rdap 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 domain_fetch_domain_rdap 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 domain_fetch_domain_rdap. 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.
domain_fetch_domain_rdap is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue