openclaw_node_command
${DEPRECATED} Run a command on an OpenClaw node.
This record as markdown: /tools/yuga-hashimoto-localant/openclaw-node-command.md
What openclaw_node_command does on LocalAnt
AI agents invoke openclaw_node_command to trigger actions in LocalAnt. 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 openclaw_node_command is rated High
This tool runs arbitrary commands on an OpenClaw node, making it Execute rather than Read (it has side effects), Write (effects may be destructive or unpredictable), or Financial (no money movement).
From the tool's definition Tool description states 'Run a command on an OpenClaw node' — this explicitly triggers command execution on a remote system, which qualifies as Execute category per the definitions.
Attacks that exploit this kind of access
The rule that runs openclaw_node_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openclaw_node_command, this is the rule to start with:
openclaw_node_command 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.
The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every openclaw_node_command call is checked against it from then on.
Questions about openclaw_node_command
${DEPRECATED} Run a command on an OpenClaw node. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LocalAnt MCP server in PolicyLayer and add a rule for openclaw_node_command: 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 LocalAnt. Nothing to install.
openclaw_node_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the openclaw_node_command 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.
Set action: deny in the PolicyLayer policy for openclaw_node_command. 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.
openclaw_node_command is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue