AI agents call dig_dns 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 dig command is a standard DNS lookup utility that queries nameservers and returns DNS records (A, MX, NS, etc.). This is purely informational retrieval with no side effects—no data is created, modified, deleted, or executed. While the tool exists in a penetration testing context (Kali Linux), its function itself is passive reconnaissance, making it a Read operation with low severity.
From the tool's definition Tool name 'dig_dns' and description 'Perform DNS lookup using dig command' indicate a query operation that retrieves DNS information without modifying or executing code.
Attacks that exploit this kind of access
Perform DNS lookup using dig command. 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 dig_dns: 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.
dig_dns 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 dig_dns 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 dig_dns. 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.
dig_dns is provided by the Kali MCP server (rangta10/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 →