Query XMemo audit events. Requires an API key with audit scope.
AI agents call xmemo_audit_events 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 is fundamentally a read/query operation (no data modification), so it belongs in the Read category. Severity is elevated to 'high' rather than 'low' because: (1) audit logs are sensitive and typically restricted (requires 'audit scope' API key), (2) unrestricted querying could expose system internals, user behavior, and security events that an AI agent should not access without strict guardrails, and (3) the…
From the tool's definition Tool description states 'Query XMemo audit events' — a retrieval operation. However, audit events often contain sensitive operational records, authentication logs, and system state changes that could reveal system configuration, user actions, and…
Attacks that exploit this kind of access
Query XMemo audit events. Requires an API key with audit scope. 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 xmemo_audit_events: 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_audit_events 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 xmemo_audit_events 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_audit_events. 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_audit_events 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_audit_events 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 →