Low Risk

whois_domain

Looksup whois information about the domain

How to control whois_domain ↓

What whois_domain does on Whois MCP

AI agents call whois_domain to retrieve information from Whois MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why whois_domain needs a policy

This tool queries and retrieves public WHOIS data about domains. It has no side effects, does not modify data, and does not execute code or commands. The blast radius of misuse is minimal—an agent could only retrieve publicly available registration information. This is a straightforward read/query operation.

From the tool's definition Tool performs 'whois lookup' and 'retrieves domain registration details, including ownership, registration dates, and availability status'. No modification, deletion, or code execution occurs.

Documented attack patterns abuse exactly the kind of access whois_domain gives an agent:

How to control whois_domain

PolicyLayer is an MCP gateway — it sits between your AI agents and Whois MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for whois_domain:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "whois_domain": {}
  }
}

whois_domain is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Whois MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about whois_domain

What does the whois_domain tool do? +

Looksup whois information about the domain. It is categorised as a Read tool in the Whois MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on whois_domain? +

Register the Whois MCP server in PolicyLayer and add a rule for whois_domain: 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 Whois MCP. Nothing to install.

What risk level is whois_domain? +

whois_domain is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit whois_domain? +

Yes. Add a rate_limit block to the whois_domain 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.

How do I block whois_domain completely? +

Set action: deny in the PolicyLayer policy for whois_domain. 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.

What MCP server provides whois_domain? +

whois_domain is provided by the Whois MCP server (modelcontextprotocol-servers/whois-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Whois MCP tool call.

Start from Whois MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 Whois MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.