This record as markdown: /tools/openclaw/dreaming.md
What dreaming does on OpenClaw
AI agents use dreaming 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 dreaming is rated Medium
The tool modifies a system state (enables or disables a feature called 'memory dreaming'). This is a reversible write operation — toggling a configuration setting. The exact nature of 'memory dreaming' is unclear from the description alone, but the enable/disable pattern is a classic Write action. Severity is medium because misuse could affect memory/agent behavior, but it appears reversible.
From the tool's definition 'Enable or disable memory dreaming' indicates toggling a state/feature on or off, which is a reversible configuration change.
Attacks that exploit this kind of access
The rule that runs dreaming 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 dreaming, this is the rule to start with:
dreaming 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 dreaming call is checked against it from then on.
Questions about dreaming
Enable or disable memory dreaming. 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 dreaming: 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.
dreaming 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 dreaming 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 dreaming. 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.
dreaming 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