tcp_scan

Perform a TCP connect scan 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/tcp-scan.md

WHAT IT DOES

What tcp_scan does on NmapMCP

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

A TCP connect scan actively probes remote systems by establishing TCP connections, which is an external network operation with real side effects (network traffic, logging on target systems, potential IDS alerts). This is classic active reconnaissance/execution. It doesn't merely read local data — it executes network-level actions against potentially arbitrary targets.

From the tool's definition 'Perform a TCP connect scan on the specified target' — actively initiates TCP connections to remote hosts, triggering external network operations

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tcp_scan Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tcp_scan": {
      "limits": [
        {
          "counter": "tcp_scan_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 tcp_scan call is checked against it from then on.

FAQ

Questions about tcp_scan

What does the tcp_scan tool do? +

Perform a TCP connect scan 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 tcp_scan? +

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

What risk level is tcp_scan? +

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

Can I rate-limit tcp_scan? +

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

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

tcp_scan 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

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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