store_memory · Claude Session Continuity MCP: Risk & Policy

WHAT IT DOES

What store_memory does on Claude Session Continuity

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

WHY IT NEEDS A POLICY

Why store_memory needs a policy

This tool writes/stores data (knowledge, decisions, learned information) into a persistent memory store. It creates or modifies stored context data reversibly. While it could influence future AI behavior by persisting decisions, it does not execute code, delete data, or involve financial operations. The blast radius is medium because stored memories could subtly influence future session behavior if misused.

From the tool's definition "새로운 지식/학습/결정 사항을 메모리에 저장합니다" (Stores new knowledge/learning/decisions in memory) and "Claude가 배운 것들을 기억합니다" (Claude remembers what it has learned)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

store_memory Rate-limited

store_memory 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": {
    "store_memory": {
      "limits": [
        {
          "counter": "store_memory_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 Session Continuity, so you can run agents against it safely.

FAQ

Questions about store_memory

What does the store_memory tool do? +

새로운 지식/학습/결정 사항을 메모리에 저장합니다. Claude가 배운 것들을 기억합니다. It is categorised as a Write tool in the Claude Session Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on store_memory? +

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

What risk level is store_memory? +

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

Can I rate-limit store_memory? +

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

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

store_memory is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.