AI agents call whois_scan to retrieve information from Kali without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The whois command is a standard information-gathering utility that queries public databases to retrieve metadata about domain names and IP addresses. It performs read-only lookups with no side effects, data modification, or destructive capability. While the server context involves penetration testing tools, whois itself is purely informational reconnaissance with no capability to alter systems or data.
From the tool's definition Tool name 'whois_scan' and description 'Execute whois with the provided parameters' indicates running the whois command, which retrieves publicly available domain registration and network ownership information without modifying data.
Attacks that exploit this kind of access
Execute whois with the provided parameters. It is categorised as a Read tool in the Kali MCP Server, which means it retrieves data without modifying state.
Register the Kali MCP server in PolicyLayer and add a rule for whois_scan: 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 Kali. Nothing to install.
whois_scan 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_scan 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_scan. 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_scan is provided by the Kali MCP server (pentestt00ls/kali-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 →