session_restore · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What session_restore does on Claude Flow

AI agents use session_restore to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.

WHY IT NEEDS A POLICY

Why session_restore needs a policy

session_restore modifies runtime state by restoring agent definitions, swarm topology, memory store, and breaker history from a saved checkpoint. These are reversible writes that alter the execution environment and internal state of the orchestration system.

From the tool's definition Restore a saved session...restoring agent definitions, swarm topology, memory store, breaker history.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

session_restore Rate-limited

session_restore 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": {
    "session_restore": {
      "limits": [
        {
          "counter": "session_restore_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about session_restore

What does the session_restore tool do? +

Restore a saved session Use when native conversation memory is wrong because you need durable cross-session state — restoring agent definitions, swarm topology, memory store, breaker history. For in-session continuation only, no tool needed. Pair with session_save before exiting and session_restore on resume. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on session_restore? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for session_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 Claude Flow. Nothing to install.

What risk level is session_restore? +

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

Can I rate-limit session_restore? +

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

Set action: deny in the PolicyLayer policy for session_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 session_restore? +

session_restore is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.