# whois_lookup

Get WHOIS information for a domain

Agent View of the PolicyLayer registry record for `whois_lookup`. HTML page: https://policylayer.com/tools/deshabhishek007-domain-tools-mcp-server/whois-lookup

## Facts

- Tool: `whois_lookup`
- Server: Domain Tools MCP Server (`deshabhishek007/domain-tools-mcp-server`) — https://policylayer.com/tools/deshabhishek007-domain-tools-mcp-server.md
- Homepage: https://github.com/deshabhishek007/domain-tools-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "whois_lookup",
    "arguments": {}
  }
}
```

## Why whois_lookup is rated Low

WHOIS lookups are read-only queries that return public domain registration information (registrar, registrant contact, nameservers, etc.). They have no side effects, cannot modify or delete data, and pose minimal security risk even if misused by an AI agent. The worst outcome would be information gathering, which is inherently low-impact.

From the tool's own definition: "The tool is described as 'Get WHOIS information for a domain' — it retrieves publicly available registration data with no modification, deletion, or execution capability."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Domain Tools MCP Server:

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

## Other tools on Domain Tools MCP Server (3)

- `dns_health_check` — Read — https://policylayer.com/tools/deshabhishek007-domain-tools-mcp-server/dns-health-check.md
- `dns_records` — Read — https://policylayer.com/tools/deshabhishek007-domain-tools-mcp-server/dns-records.md
- `domain_analysis` — Read — https://policylayer.com/tools/deshabhishek007-domain-tools-mcp-server/domain-analysis.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deshabhishek007-domain-tools-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deshabhishek007-domain-tools-mcp-server