manage_session_state · Chronicle MCP: Risk & Policy

WHAT IT DOES

What manage_session_state does on Chronicle MCP

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

WHY IT NEEDS A POLICY

Why manage_session_state needs a policy

The tool predominantly performs reversible modifications to session state: saving, auto-saving, merging sessions, and exporting to markdown are all write operations that can be undone or overwritten. While 'delete' appears as an option and would normally elevate this to Destructive, the tool's core purpose centers on session management with write operations.

From the tool's definition Tool provides 'save', 'register_auto_save', 'trigger_auto_save', 'merge', and 'export_markdown' actions that create or modify session data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_session_state Rate-limited

manage_session_state 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": {
    "manage_session_state": {
      "limits": [
        {
          "counter": "manage_session_state_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 Chronicle MCP, so you can run agents against it safely.

FAQ

Questions about manage_session_state

What does the manage_session_state tool do? +

Manage session auto-saving, folder watching, merging, exporting, and deletion. Options for action: 'save', 'register_auto_save', 'trigger_auto_save', 'watch_folder', 'merge', 'export_markdown', 'delete'. It is categorised as a Write tool in the Chronicle MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_session_state? +

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

What risk level is manage_session_state? +

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

Can I rate-limit manage_session_state? +

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

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

manage_session_state is provided by the Chronicle MCP server (pypi:chronicle-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.