AI agents invoke dnsenum_scan to trigger actions in Kali. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
dnsenum is a DNS enumeration tool used to gather DNS information about a target domain (zone transfers, subdomains, MX records, etc.). It executes an external tool/command against a target. While it is primarily a reconnaissance/read operation, it runs an active external program against potentially unauthorized targets, classifying it as Execute.
From the tool's definition 'Execute dnsenum with the provided parameters' on a Kali Linux penetration testing server supporting 'network scanning' and security assessment tools
Attacks that exploit this kind of access
Execute dnsenum with the provided parameters. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for dnsenum_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.
dnsenum_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dnsenum_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 dnsenum_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.
dnsenum_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.
dnsenum_scan is one line of Kali's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →