This record as markdown: /tools/openclaw/abort.md
What abort does on OpenClaw
AI agents invoke abort 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 abort is rated High
Aborting an active run is an Execute-category action because it triggers a command to stop external operations in progress. While not destructive in the sense of permanent data loss, it can disrupt workflows and has uncontrollable side effects depending on what process is being aborted. The high severity reflects potential impact on system stability and ongoing operations.
From the tool's definition Tool name 'abort' with description 'Abort active run' indicates it triggers an external operation that terminates or interrupts an active process or workflow. This is an execution action that causes immediate effects on running systems.
Attacks that exploit this kind of access
The rule that runs abort 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 abort, this is the rule to start with:
abort 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 abort call is checked against it from then on.
Questions about abort
Abort active run. 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 abort: 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.
abort 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 abort 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 abort. 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.
abort 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