active-memory
Enable, disable, or inspect Active Memory for this session.
This record as markdown: /tools/openclaw/active-memory.md
What active-memory does on OpenClaw
AI agents use active-memory 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 active-memory is rated Medium
The tool modifies session-level configuration (enabling/disabling Active Memory) which constitutes a Write operation. It is reversible (can be toggled on/off), so not Destructive. The 'inspect' capability is a Read component, but the write actions dominate.
From the tool's definition The tool enables, disables, or inspects Active Memory for this session, implying state modification capability. The presence of 'Enable' and 'disable' actions indicates reversible changes to session state.
Attacks that exploit this kind of access
The rule that runs active-memory 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 active-memory, this is the rule to start with:
active-memory 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 active-memory call is checked against it from then on.
Questions about active-memory
Enable, disable, or inspect Active Memory for this session. 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 active-memory: 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.
active-memory 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 active-memory 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 active-memory. 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.
active-memory 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