nodes

Pair nodes and run node-host commands through the Gateway

SERVEROpenClaw SOURCEopenclaw

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/openclaw/nodes.md

WHAT IT DOES

What nodes does on OpenClaw

AI agents invoke nodes to trigger actions in OpenClaw. 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.

RISK

Why nodes is rated High

Running commands on remote nodes is an Execute operation because it triggers external operations whose effects depend on the arguments supplied. The ability to run arbitrary 'node-host commands' suggests code/command execution capability. Severity is high because command execution on infrastructure can have broad impact, though not marked critical without evidence of destructive or financial operations.

From the tool's definition The tool description states it can 'run node-host commands through the Gateway', indicating execution of arbitrary commands on nodes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nodes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nodes, this is the rule to start with:

nodes Rate-limited

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": {
    "nodes": {
      "limits": [
        {
          "counter": "nodes_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every nodes call is checked against it from then on.

FAQ

Questions about nodes

What does the nodes tool do? +

Pair nodes and run node-host commands through the Gateway. It is categorised as a Execute tool in the OpenClaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nodes? +

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

What risk level is nodes? +

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

Can I rate-limit nodes? +

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

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

nodes is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OpenClaw, and thousands of servers like it.

This server

All 129 OpenClaw tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →