Look up domain registration data over the raw WHOIS protocol (port 43): registrar, creation/update/expiry dates, name servers and domain status. Resolves the correct WHOIS server via IANA and follows registrar referrals. No API key. Args: - domain (string): the domain to look up. - response_format (
AI agents call whois_lookup to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
WHOIS lookups are passive information retrieval operations that query publicly available domain registration databases. No data is modified, deleted, or at risk of financial impact. The blast radius of misuse is minimal—an agent could enumerate domains or perform reconnaissance, but cannot cause damage through this tool alone. This is a standard Read category security audit tool.
From the tool's definition Tool performs 'Look up domain registration data' and 'Resolves the correct WHOIS server via IANA' — these are read-only information retrieval operations. The description contains no mutative verbs like create, update, delete, execute, or pay.
Attacks that exploit this kind of access
Look up domain registration data over the raw WHOIS protocol (port 43): registrar, creation/update/expiry dates, name servers and domain status. Resolves the correct WHOIS server via IANA and follows registrar referrals. No API key. Args: - domain (string): the domain to look up. - response_format (. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.
Register the Domain Security 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 Security. Nothing to install.
whois_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 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.
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.
whois_lookup is provided by the Domain Security MCP server (ortamarco/domain-security-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →