osDetection · Linux Network Scanner MCP Server MCP

WHAT IT DOES

What osDetection does on Linux Network Scanner MCP Server

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

OS detection typically involves sending crafted network packets to remote hosts to fingerprint their operating system, which is an active network operation with external effects. The server context (nmap-based scanning, sibling tools like exploitScan and ftpBruteForce) confirms this is an Execute-category action.

From the tool's definition Tool name 'osDetection' on a server described as using nmap for 'OS detection' and 'network security scanning'; sibling tools include exploitScan, ftpBruteForce, and directCmd indicating active scanning/execution capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

osDetection Rate-limited

osDetection 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": {
    "osDetection": {
      "limits": [
        {
          "counter": "osdetection_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 osDetection

What does the osDetection tool do? +

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

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

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

Can I rate-limit osDetection? +

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

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

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