routerScan · Linux Network Scanner MCP Server MCP

WHAT IT DOES

What routerScan does on Linux Network Scanner MCP Server

AI agents invoke routerScan to trigger actions in Linux Network Scanner MCP Server. 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 IT NEEDS A POLICY

Why routerScan needs a policy

Although the tool description is empty, the context of the server (offensive security toolset including exploit and brute-force tools) and the tool name strongly suggest this executes active network scanning against routers. Router scanning has a high blast radius: it can expose network topology, credentials, and vulnerabilities, and active scanning may disrupt network devices.

From the tool's definition Tool name 'routerScan' on a server with siblings like 'exploitScan', 'ftpBruteForce', 'bettercapScan', 'aircrackScan', and 'cmd'/'directCmd' — all offensive security tools. Server description mentions nmap-based scanning, port scanning, OS detection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

routerScan Rate-limited

routerScan 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": {
    "routerScan": {
      "limits": [
        {
          "counter": "routerscan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linux Network Scanner MCP Server, so you can run agents against it safely.

FAQ

Questions about routerScan

What does the routerScan tool do? +

routerScan. It is categorised as a Execute tool in the Linux Network Scanner MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on routerScan? +

Register the Linux Network Scanner MCP Server MCP server in PolicyLayer and add a rule for routerScan: 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 Linux Network Scanner MCP Server. Nothing to install.

What risk level is routerScan? +

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

Can I rate-limit routerScan? +

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

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

routerScan is provided by the Linux Network Scanner MCP Server MCP server (nibesh0/netsecmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.