domains.lookup
Look up a domain and return normalized registration details. Combines registry and registrar RDAP and WHOIS sources to return the most accurate normalized fields across TLDs: availability, domain status, created/updated/expiry dates, registrar data, contact records, and nameservers. Use this when...
This record as markdown: /tools/io-github-vee3io-vee3/domains.lookup.md
What domains.lookup does on Vee3
AI agents call domains.lookup 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). |
Parameters from the server's own tool schema.
Why domains.lookup is rated Low
This tool retrieves and queries domain registration information without creating, modifying, deleting, or executing actions. It is fundamentally a Read operation. Severity is medium rather than low because WHOIS/RDAP data can include sensitive registrant contact information (names, addresses, emails, phone numbers), which could enable privacy violations, phishing, or social engineering if misused by an agent to…
From the tool's definition Tool description states it 'Look[s] up a domain and return[s] normalized registration details' from 'registry and registrar RDAP and WHOIS sources.' The verb is 'return,' indicating data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs domains.lookup 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.lookup, this is the rule to start with:
domains.lookup 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.lookup call is checked against it from then on.
Questions about domains.lookup
Look up a domain and return normalized registration details. Combines registry and registrar RDAP and WHOIS sources to return the most accurate normalized fields across TLDs: availability, domain status, created/updated/expiry dates, registrar data, contact records, and nameservers. Use this when you need registrant-oriented summary data rather than raw WHOIS or RDAP payloads. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
domains.lookup accepts 1 parameter: domain. 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.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 Vee3. Nothing to install.
domains.lookup 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.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.
Set action: deny in the PolicyLayer policy for domains.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.
domains.lookup 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