New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dnsrecon_scan

A execute tool on the Kali Security MCP server.

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/dnsrecon-scan.md

What dnsrecon_scan does on Kali Security MCP

AI agents invoke dnsrecon_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.

Why dnsrecon_scan is rated High

dnsrecon is a well-known Kali Linux DNS reconnaissance tool that performs active DNS enumeration against target domains. Given the server context (penetration testing, Kali tools), this tool likely executes dnsrecon against external targets. Empty description lowers confidence, but the tool name and server context strongly imply active execution of a security scanning tool.

From the tool's definition Tool name 'dnsrecon_scan' on a server described as integrating 193 Kali Linux security tools for penetration testing; description is empty.

Questions about dnsrecon_scan

What does the dnsrecon_scan tool do? +

dnsrecon_scan is a execute tool on the Kali Security MCP server. 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.

How do I enforce a policy on dnsrecon_scan? +

Register the Kali Security MCP server in PolicyLayer and add a rule for dnsrecon_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.

What risk level is dnsrecon_scan? +

dnsrecon_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dnsrecon_scan? +

Yes. Add a rate_limit block to the dnsrecon_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.

How do I block dnsrecon_scan completely? +

Set action: deny in the PolicyLayer policy for dnsrecon_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.

What MCP server provides dnsrecon_scan? +

dnsrecon_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.

More on Kali Security, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kali Security's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.