Low Risk

run_whois_lookup

perform query of domain ownership details.

How to control run_whois_lookup ↓

What run_whois_lookup does on External Reconnaissance MCP Server

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

Low Risk

Why run_whois_lookup needs a policy

WHOIS lookups are read-only queries that retrieve publicly available domain registration information (owner, registrar, dates, nameservers). No data is created or modified. However, the broader server context (external reconnaissance) elevates severity to medium, as this tool is part of an active reconnaissance toolkit that could be used to gather intelligence on targets without authorization.

From the tool's definition 'perform query of domain ownership details' — this is a passive lookup/read operation retrieving publicly available WHOIS registration data

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

How to control run_whois_lookup

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

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

run_whois_lookup 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 External Reconnaissance MCP Server — 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 run_whois_lookup

What does the run_whois_lookup tool do? +

perform query of domain ownership details. It is categorised as a Read tool in the External Reconnaissance MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on run_whois_lookup? +

Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for run_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 External Reconnaissance MCP Server. Nothing to install.

What risk level is run_whois_lookup? +

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

Can I rate-limit run_whois_lookup? +

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

How do I block run_whois_lookup completely? +

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

What MCP server provides run_whois_lookup? +

run_whois_lookup is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every External Reconnaissance MCP Server tool call.

Start from External Reconnaissance MCP Server, 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.

8 External Reconnaissance MCP Server 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.