xmemo_restart_snapshot_save · Openclaw Memory MCP

WHAT IT DOES

What xmemo_restart_snapshot_save does on Openclaw Memory

AI agents use xmemo_restart_snapshot_save 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.

WHY IT NEEDS A POLICY

Why xmemo_restart_snapshot_save needs a policy

This tool writes/saves session state data to XMemo cloud storage. It creates a new snapshot record, which is a reversible write operation (the snapshot can presumably be deleted or overwritten later). It does not execute code, delete data, or involve financial transactions.

From the tool's definition Save a restart snapshot to XMemo so the current session state can be restored later.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xmemo_restart_snapshot_save Rate-limited

xmemo_restart_snapshot_save 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "xmemo_restart_snapshot_save": {
      "limits": [
        {
          "counter": "xmemo_restart_snapshot_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Openclaw Memory, so you can run agents against it safely.

FAQ

Questions about xmemo_restart_snapshot_save

What does the xmemo_restart_snapshot_save tool do? +

Save a restart snapshot to XMemo so the current session state can be restored later. 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.

How do I enforce a policy on xmemo_restart_snapshot_save? +

Register the Openclaw Memory MCP server in PolicyLayer and add a rule for xmemo_restart_snapshot_save: 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.

What risk level is xmemo_restart_snapshot_save? +

xmemo_restart_snapshot_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit xmemo_restart_snapshot_save? +

Yes. Add a rate_limit block to the xmemo_restart_snapshot_save 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.

How do I block xmemo_restart_snapshot_save completely? +

Set action: deny in the PolicyLayer policy for xmemo_restart_snapshot_save. 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.

What MCP server provides xmemo_restart_snapshot_save? +

xmemo_restart_snapshot_save 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.

// THE FULL RECORD

xmemo_restart_snapshot_save 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 →