save_session_history · Claude Session Continuity MCP

WHAT IT DOES

What save_session_history does on Claude Session Continuity

AI agents use save_session_history 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 save_session_history needs a policy

This tool writes/persists session history data to a database. While not destructive (data can be overwritten or cleared), it modifies stored state. The medium severity reflects that misuse could corrupt project context across sessions, impacting development workflow, but doesn't cause irreversible harm or financial impact. Confidence is slightly reduced due to the Korean-language description, but the intent is clear.

From the tool's definition Tool description states '세션 기록을 DB에 저장합니다' (saves session history to DB) and is automatically called during update_session, indicating it creates or modifies data persistently in a database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_session_history Rate-limited

save_session_history 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": {
    "save_session_history": {
      "limits": [
        {
          "counter": "save_session_history_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 save_session_history

What does the save_session_history tool do? +

세션 기록을 DB에 저장합니다. update_session 호출 시 자동으로 호출됩니다. 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 save_session_history? +

Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for save_session_history: 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 save_session_history? +

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

Can I rate-limit save_session_history? +

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

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

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