update_session · Claude Session Continuity MCP

WHAT IT DOES

What update_session does on Claude Session Continuity

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

This tool creates or modifies data reversibly: it updates a project's SESSION.md file and persists changes to a database. These are write operations with side effects but are not destructive (changes can be undone/rolled back) or irreversible. The blast radius is medium because misconfigured session data could disrupt project continuity, but the operation itself is reversible.

From the tool's definition Tool description states it 'updates PROJECT SESSION.md' and 'saves history to DB' — explicit write operations that modify files and database records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_session Rate-limited

update_session 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": {
    "update_session": {
      "limits": [
        {
          "counter": "update_session_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 update_session

What does the update_session tool do? +

프로젝트의 SESSION.md를 업데이트하고 DB에 이력을 저장합니다. 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 update_session? +

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

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

Can I rate-limit update_session? +

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

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

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