exploitScan · Linux Network Scanner MCP Server MCP

WHAT IT DOES

What exploitScan does on Linux Network Scanner MCP Server

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

Despite an empty description, the tool name 'exploitScan' combined with the server context (offensive security tools including brute force, wireless cracking, and direct command execution) indicates this tool likely runs exploit code or exploit frameworks (e.g., Metasploit) against targets. This is Execute-category at minimum, with critical severity due to the potential to compromise remote systems.

From the tool's definition Tool name 'exploitScan' on a server with sibling tools like 'ftpBruteForce', 'aircrackScan', 'bettercapScan', and 'directCmd' — all offensive security tools. The server description mentions 'vulnerability assessment' and 'authorized security testing'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

exploitScan Rate-limited

exploitScan 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": {
    "exploitScan": {
      "limits": [
        {
          "counter": "exploitscan_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 exploitScan

What does the exploitScan tool do? +

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

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

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

Can I rate-limit exploitScan? +

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

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

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