dns_brute_force

Perform DNS brute-force to discover subdomains of the specified target.

SERVERNmapMCP SOURCE0xpratikpatil/nmapmcp

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/0xpratikpatil-nmapmcp/dns-brute-force.md

WHAT IT DOES

What dns_brute_force does on NmapMCP

AI agents invoke dns_brute_force to trigger actions in NmapMCP. 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.

RISK

Why dns_brute_force is rated High

DNS brute-force actively sends large volumes of DNS queries against an external target to enumerate subdomains. This is an active reconnaissance operation that triggers external network activity and could be considered intrusive or hostile against targets without authorization.

From the tool's definition "Perform DNS brute-force to discover subdomains of the specified target"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dns_brute_force safely

PolicyLayer is an MCP gateway: it sits between your AI agents and NmapMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_brute_force, this is the rule to start with:

dns_brute_force Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_brute_force": {
      "limits": [
        {
          "counter": "dns_brute_force_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect NmapMCP, apply this rule, and every dns_brute_force call is checked against it from then on.

FAQ

Questions about dns_brute_force

What does the dns_brute_force tool do? +

Perform DNS brute-force to discover subdomains of the specified target. It is categorised as a Execute tool in the NmapMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dns_brute_force? +

Register the Nmap MCP server in PolicyLayer and add a rule for dns_brute_force: 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 NmapMCP. Nothing to install.

What risk level is dns_brute_force? +

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

Can I rate-limit dns_brute_force? +

Yes. Add a rate_limit block to the dns_brute_force 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 dns_brute_force completely? +

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

dns_brute_force is provided by the Nmap MCP server (0xpratikpatil/nmapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nmap, and thousands of servers like it.

This server

All 15 Nmap tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →