This record as markdown: /tools/openclaw/queue.md
What queue does on OpenClaw
AI agents use queue to create or update resources in OpenClaw, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenClaw environment.
Why queue is rated Medium
Adjusting queue mode and options constitutes creating or modifying data in a reversible manner. This is a Write action because changes to queue configuration can typically be undone or reverted. Severity is medium because misuse could disrupt workflow or operations, but the impact is not typically irreversible (Destructive) or code execution (Execute).
From the tool's definition Tool name 'queue' with description 'Adjust queue mode and options' indicates modification of queue configuration/state. The verb 'adjust' directly implies writing/changing settings.
Attacks that exploit this kind of access
The rule that runs queue 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 queue, this is the rule to start with:
queue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 queue call is checked against it from then on.
Questions about queue
Adjust queue mode and options. It is categorised as a Write tool in the OpenClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenClaw MCP server in PolicyLayer and add a rule for queue: 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.
queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the queue 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 queue. 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.
queue 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