xmemo_restart_snapshot_restore · Openclaw Memory MCP

WHAT IT DOES

What xmemo_restart_snapshot_restore does on Openclaw Memory

AI agents invoke xmemo_restart_snapshot_restore to trigger actions in Openclaw Memory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why xmemo_restart_snapshot_restore needs a policy

xmemo_restart_snapshot_restore triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xmemo_restart_snapshot_restore Rate-limited

xmemo_restart_snapshot_restore stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_restore": {
      "limits": [
        {
          "counter": "xmemo_restart_snapshot_restore_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_restore

What does the xmemo_restart_snapshot_restore tool do? +

Restore a previous restart snapshot from XMemo. It is categorised as a Execute tool in the Openclaw Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xmemo_restart_snapshot_restore? +

Register the Openclaw Memory MCP server in PolicyLayer and add a rule for xmemo_restart_snapshot_restore: 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_restore? +

xmemo_restart_snapshot_restore is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit xmemo_restart_snapshot_restore? +

Yes. Add a rate_limit block to the xmemo_restart_snapshot_restore 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_restore completely? +

Set action: deny in the PolicyLayer policy for xmemo_restart_snapshot_restore. 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_restore? +

xmemo_restart_snapshot_restore 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_restore 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 →