This record as markdown: /tools/openclaw/commands.md
What commands does on OpenClaw
AI agents call commands to retrieve information from OpenClaw without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why commands is rated Low
This is a read-only informational tool that enumerates or retrieves command metadata. It has no side effects, does not execute code, does not modify data, and does not commit financial or destructive operations. The blast radius of misuse is minimal—an AI agent listing commands cannot cause harm beyond gaining knowledge of what commands exist.
From the tool's definition Tool name 'commands' and description 'List available commands' indicate a query/listing operation that retrieves information about available commands without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs commands 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 commands, this is the rule to start with:
commands is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every commands call is checked against it from then on.
Questions about commands
List available commands. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP server in PolicyLayer and add a rule for commands: 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.
commands is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the commands 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 commands. 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.
commands 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.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue