Read a specific XMemo memory by its path. The path is returned by memory_search and encodes the XMemo memory id.
AI agents call memory_get to retrieve information from Openclaw Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored memory data by identifier. It is a lookup/fetch operation that does not create, modify, delete, or execute external operations. The 'Read' category is appropriate for data retrieval tools. Severity is low because reading memory data alone poses minimal risk; the worst case is information disclosure, which is less severe than write or destructive operations.
From the tool's definition Tool description states 'Read a specific XMemo memory by its path' — explicit read operation with no modification or side effects. Returns data based on a path argument.
Attacks that exploit this kind of access
Read a specific XMemo memory by its path. The path is returned by memory_search and encodes the XMemo memory id. It is categorised as a Read tool in the Openclaw Memory MCP Server, which means it retrieves data without modifying state.
Register the Openclaw Memory MCP server in PolicyLayer and add a rule for memory_get: 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 Memory. Nothing to install.
memory_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_get 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 memory_get. 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.
memory_get is provided by the Openclaw Memory MCP server (@xmemo/openclaw-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
memory_get is one line of Openclaw Memory's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →