scan_network · MCP Shamash MCP: Risk & Policy

WHAT IT DOES

What scan_network does on MCP Shamash

AI agents invoke scan_network to trigger actions in MCP Shamash. 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 scan_network needs a policy

Network scanning is an active operation that sends probes/packets to external systems, making it Execute rather than Read. It can trigger IDS/IPS alerts, affect network devices, and if misused or pointed at unintended targets (even within 'project boundaries'), could cause disruption or legal issues.

From the tool's definition "Performs network scanning within project boundaries" — actively executes network reconnaissance operations against targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_network Rate-limited

scan_network 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": {
    "scan_network": {
      "limits": [
        {
          "counter": "scan_network_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 MCP Shamash, so you can run agents against it safely.

FAQ

Questions about scan_network

What does the scan_network tool do? +

Performs network scanning within project boundaries. It is categorised as a Execute tool in the MCP Shamash MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_network? +

Register the MCP Shamash MCP server in PolicyLayer and add a rule for scan_network: 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 MCP Shamash. Nothing to install.

What risk level is scan_network? +

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

Can I rate-limit scan_network? +

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

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

scan_network is provided by the MCP Shamash MCP server (neotecdigital/mcp_shamash). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.