set_current_session · MCP Claude Context Continuity MCP

WHAT IT DOES

What set_current_session does on MCP Claude Context Continuity

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

WHY IT NEEDS A POLICY

Why set_current_session needs a policy

This tool creates or modifies session state by designating which session is current. While it doesn't directly execute code or delete data, it alters the execution context that downstream tools (execute_claude, execute_claude_with_context) will operate within. If an AI agent sets the wrong session, it could cause subsequent operations to run in an unintended context, affecting data integrity and execution flow.

From the tool's definition Tool name 'set_current_session' and description indicating it sets a session ID. Sibling tools include 'execute_claude', 'execute_claude_with_context', 'get_execution_history', and 'clear_execution_history', indicating this server manages execution state and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_current_session Rate-limited

set_current_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": {
    "set_current_session": {
      "limits": [
        {
          "counter": "set_current_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 MCP Claude Context Continuity, so you can run agents against it safely.

FAQ

Questions about set_current_session

What does the set_current_session tool do? +

セッションIDを即座に設定（実行は一瞬で完了）. It is categorised as a Write tool in the MCP Claude Context 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 set_current_session? +

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

What risk level is set_current_session? +

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

Can I rate-limit set_current_session? +

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

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

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