disable_dns_resolution

A execute tool on the Nmap MCP server.

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/disable-dns-resolution.md

WHAT IT DOES

What disable_dns_resolution does on NmapMCP

AI agents invoke disable_dns_resolution 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 disable_dns_resolution is rated High

Based on context from the NmapMCP server, this tool likely modifies Nmap scan behavior by disabling DNS resolution (-n flag), which is an execution-affecting configuration for active network reconnaissance. Empty description lowers confidence. Classified as Execute due to its role in triggering/modifying network scan operations, with medium severity as it facilitates reconnaissance activities.

From the tool's definition Tool name: 'disable_dns_resolution'; description is empty. Sibling tools include port scanning, OS detection, DNS brute force — all active network operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disable_dns_resolution 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 disable_dns_resolution, this is the rule to start with:

disable_dns_resolution Rate-limited

disable_dns_resolution 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": {
    "disable_dns_resolution": {
      "limits": [
        {
          "counter": "disable_dns_resolution_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 disable_dns_resolution call is checked against it from then on.

FAQ

Questions about disable_dns_resolution

What does the disable_dns_resolution tool do? +

disable_dns_resolution is a execute tool on the Nmap MCP server. 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 disable_dns_resolution? +

Register the Nmap MCP server in PolicyLayer and add a rule for disable_dns_resolution: 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 disable_dns_resolution? +

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

Can I rate-limit disable_dns_resolution? +

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

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

disable_dns_resolution 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

disable_modsecurity on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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