version_detection

Detect service versions on the specified target with optional custom arguments.

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/version-detection.md

WHAT IT DOES

What version_detection does on NmapMCP

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

Version detection actively probes network services on a target to identify running software and versions. This constitutes active reconnaissance/scanning which triggers external operations against remote systems. The 'optional custom arguments' increases risk as it allows arbitrary Nmap flags. In context of a network scanning MCP server, this could be misused for unauthorized reconnaissance, making it high severity.

From the tool's definition Detect service versions on the specified target with optional custom arguments

Attacks that exploit this kind of access

RECOMMENDED RULE

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

version_detection Rate-limited

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

FAQ

Questions about version_detection

What does the version_detection tool do? +

Detect service versions on the specified target with optional custom arguments. 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 version_detection? +

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

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

Can I rate-limit version_detection? +

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

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

version_detection 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 →