This record as markdown: /tools/openclaw/completion.md
What completion does on OpenClaw
AI agents invoke completion 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.
Why completion is rated High
Generating a shell completion script produces executable shell code. While the act of generating it may not immediately execute it, the output is a shell script intended to be sourced/executed in a shell environment. The closest category is Execute given the shell script nature, though it could also be considered Write.
From the tool's definition "Generate shell completion script" — generates a shell script artifact
Attacks that exploit this kind of access
The rule that runs completion 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 completion, this is the rule to start with:
completion 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 OpenClaw, apply this rule, and every completion call is checked against it from then on.
Questions about completion
Generate shell completion script. 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.
Register the OpenClaw MCP server in PolicyLayer and add a rule for completion: 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.
completion 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 completion 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 completion. 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.
completion 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.
Across the catalogue