Record a lightweight timeline event in XMemo. Use for milestones, decisions, or session-level notes that are useful for later recall but not a full memory.
AI agents use xmemo_record_event to create or update resources in Openclaw Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openclaw Memory environment.
This tool creates new data (timeline events/notes) in the XMemo system. It's a write operation that stores records but does not delete, execute code, or involve financial transactions. Misuse could pollute the memory/audit trail with false milestones or decisions, giving it medium severity.
From the tool's definition Record a lightweight timeline event in XMemo... milestones, decisions, or session-level notes
Attacks that exploit this kind of access
Record a lightweight timeline event in XMemo. Use for milestones, decisions, or session-level notes that are useful for later recall but not a full memory. It is categorised as a Write tool in the Openclaw Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openclaw Memory MCP server in PolicyLayer and add a rule for xmemo_record_event: 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.
xmemo_record_event 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 xmemo_record_event 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 xmemo_record_event. 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.
xmemo_record_event 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.
xmemo_record_event 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 →