Looksup whois information about the IP
AI agents call whois_ip 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.
WHOIS IP lookups query public registry databases to retrieve registration metadata. This is a read-only operation with no capability to modify, delete, or execute code. The blast radius is minimal—an agent misusing this tool can only gather public information about IP ownership and registration dates. No financial, destructive, or system-altering consequences are possible.
From the tool's definition Tool description states 'Looksup whois information about the IP' — a lookup operation that retrieves existing public WHOIS data.
Documented attack patterns abuse exactly the kind of access whois_ip gives an agent:
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_ip:
{
"version": "1",
"default": "deny",
"tools": {
"whois_ip": {}
}
}whois_ip is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Looksup whois information about the IP. It is categorised as a Read tool in the Whois MCP MCP Server, which means it retrieves data without modifying state.
Register the Whois MCP server in PolicyLayer and add a rule for whois_ip: 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.
whois_ip 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_ip 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_ip. 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_ip 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.
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.