Low Risk

whois_lookup

Get WHOIS information for a domain using RDAP protocol

How to control whois_lookup ↓

AI agents call whois_lookup to retrieve information from Domain-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

WHOIS lookups are read-only queries that retrieve publicly available domain registration metadata (registrar, registration date, nameservers, contact info, etc.). The tool has no side effects, does not modify data, execute arbitrary code, or trigger destructive operations. It is purely informational. Low severity because WHOIS data is publicly accessible and its retrieval poses minimal security risk.

From the tool's definition Tool performs WHOIS lookup via RDAP protocol to 'Get WHOIS information for a domain' — a query operation that retrieves publicly available domain registration data without modifying, executing code, or causing irreversible changes.

Documented attack patterns abuse exactly the kind of access whois_lookup gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Domain-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for whois_lookup:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "whois_lookup": {}
  }
}

whois_lookup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Domain-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the whois_lookup tool do? +

Get WHOIS information for a domain using RDAP protocol. It is categorised as a Read tool in the Domain-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on whois_lookup? +

Register the Domain- MCP server in PolicyLayer and add a rule for whois_lookup: 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 Domain-MCP. Nothing to install.

What risk level is whois_lookup? +

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

Can I rate-limit whois_lookup? +

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

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

whois_lookup is provided by the Domain- MCP server (rinadelph/domain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Domain-MCP tool call.

Deterministic rules across all 8 Domain-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 Domain-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.