vulnerabilityScan · Linux Network Scanner MCP Server MCP

WHAT IT DOES

What vulnerabilityScan does on Linux Network Scanner MCP Server

AI agents invoke vulnerabilityScan 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 vulnerabilityScan needs a policy

A vulnerability scan actively probes remote systems, runs intrusive checks, and may trigger exploits or cause service disruptions. The server context (offensive security tooling, exploit scanning, brute force tools) strongly implies active scanning rather than passive reading.

From the tool's definition Tool name 'vulnerabilityScan' on a server explicitly described as running Linux security tools like nmap for 'network security scanning and vulnerability assessment'; sibling tools include exploitScan, ftpBruteForce, bettercapScan, aircrackScan — all…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vulnerabilityScan Rate-limited

vulnerabilityScan 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": {
    "vulnerabilityScan": {
      "limits": [
        {
          "counter": "vulnerabilityscan_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 vulnerabilityScan

What does the vulnerabilityScan tool do? +

vulnerabilityScan. 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 vulnerabilityScan? +

Register the Linux Network Scanner MCP Server MCP server in PolicyLayer and add a rule for vulnerabilityScan: 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 vulnerabilityScan? +

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

Can I rate-limit vulnerabilityScan? +

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

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

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