scan_cluster_nodes · Security Scanner MCP Server MCP

WHAT IT DOES

What scan_cluster_nodes does on Security Scanner MCP Server

AI agents invoke scan_cluster_nodes to trigger actions in Security 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 scan_cluster_nodes needs a policy

This tool executes a broad vulnerability scan across all nodes in a cluster, which constitutes an active external operation with significant blast radius. Scanning all nodes could disrupt services, trigger security alerts, consume resources, and expose the infrastructure's security posture. It doesn't just read existing data — it actively probes systems, placing it in the Execute category.

From the tool's definition 'Scan all nodes in the agentic cluster for vulnerabilities' — triggers active vulnerability scanning across all cluster nodes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_cluster_nodes Rate-limited

scan_cluster_nodes 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_cluster_nodes": {
      "limits": [
        {
          "counter": "scan_cluster_nodes_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 Security Scanner MCP Server, so you can run agents against it safely.

FAQ

Questions about scan_cluster_nodes

What does the scan_cluster_nodes tool do? +

Scan all nodes in the agentic cluster for vulnerabilities. It is categorised as a Execute tool in the Security 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 scan_cluster_nodes? +

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

What risk level is scan_cluster_nodes? +

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

Can I rate-limit scan_cluster_nodes? +

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

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

scan_cluster_nodes is provided by the Security Scanner MCP Server MCP server (marc-shade/security-scanner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.