Get domain WHOIS contact
AI agents call get_whois_contact to retrieve information from Domain Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public WHOIS contact information for a domain. No data is created, modified, deleted, or destroyed. No code is executed, and no financial transactions occur. The operation is a straightforward read/query of existing domain contact metadata, making it a Read category tool with low severity since WHOIS contact data is inherently public information accessible through standard WHOIS lookup services.
From the tool's definition Tool name 'get_whois_contact' and description 'Get domain WHOIS contact' indicate a retrieval operation with no modification of state. WHOIS data is public contact information associated with domain registrations.
Attacks that exploit this kind of access
Get domain WHOIS contact. It is categorised as a Read tool in the Domain Suite MCP Server, which means it retrieves data without modifying state.
Register the Domain Suite MCP server in PolicyLayer and add a rule for get_whois_contact: 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 Suite. Nothing to install.
get_whois_contact 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 get_whois_contact 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 get_whois_contact. 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.
get_whois_contact is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). 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 →