AI agents invoke dnsenum_scan to trigger actions in Kali Security MCP. 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.
This tool runs Dnsenum, an active DNS enumeration tool that performs zone transfers, brute-force subdomain discovery, and other DNS reconnaissance against target systems. It triggers external network operations against potentially unauthorized targets. On a penetration testing server with siblings like 'ad_full_attack' and 'adaptive_network_penetration', this is clearly an offensive security tool.
From the tool's definition 使用 Dnsenum 执行 DNS 枚举 (Execute DNS enumeration using Dnsenum)
Documented attack patterns abuse exactly the kind of access dnsenum_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for dnsenum_scan:
{
"version": "1",
"default": "deny",
"tools": {
"dnsenum_scan": {
"limits": [
{
"counter": "dnsenum_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dnsenum_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
使用 Dnsenum 执行 DNS 枚举。. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security 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 Security MCP. 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 Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.