domains.whois
Fetch WHOIS registration data for a domain. Returns a JSON object keyed by WHOIS server host name. Each value contains parsed fields such as Domain Name, registrar details, dates, name servers, domain status, DNSSEC data, and raw text lines. Set include_registrar to true to query registry and reg...
This record as markdown: /tools/io-github-vee3io-vee3/domains.whois.md
What domains.whois does on Vee3
AI agents call domains.whois to retrieve information from Vee3 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 name to look up (for example example.com). |
include_registrar | boolean | — | When true, query registry and registrar WHOIS servers for more complete data. When false (default), query the registry server only. |
Parameters from the server's own tool schema.
Why domains.whois is rated Low
This tool purely retrieves publicly available WHOIS registration information for a domain. It has no side effects, does not modify any data, and only reads/queries external WHOIS servers. The blast radius of misuse is minimal as it only exposes publicly available domain registration data.
From the tool's definition Fetch WHOIS registration data for a domain... Returns a JSON object... parsed fields such as Domain Name, registrar details, dates, name servers, domain status, DNSSEC data
Attacks that exploit this kind of access
The rule that runs domains.whois safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains.whois, this is the rule to start with:
domains.whois 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 Vee3, apply this rule, and every domains.whois call is checked against it from then on.
Questions about domains.whois
Fetch WHOIS registration data for a domain. Returns a JSON object keyed by WHOIS server host name. Each value contains parsed fields such as Domain Name, registrar details, dates, name servers, domain status, DNSSEC data, and raw text lines. Set include_registrar to true to query registry and registrar servers (slower, more complete). Default false queries the registry server only. Cost = 4 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
domains.whois accepts 2 parameters: domain, include_registrar. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for domains.whois: 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 Vee3. Nothing to install.
domains.whois 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 domains.whois 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 domains.whois. 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.
domains.whois is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue