solution_record

Server Claude Session Continuity leesgit/claude-session-continuity-mcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What solution_record does on Claude Session Continuity

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

The tool writes a new record to a solutions archive database table. It creates data (error-solution pairs) reversibly — no deletion, execution, or financial impact. The blast radius is low since misuse would only pollute the solutions table with duplicate or incorrect entries.

From the tool's definition inserts into the solutions table

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

solution_record Rate-limited

solution_record 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": {
    "solution_record": {
      "limits": [
        {
          "counter": "solution_record_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 solution_record

What does the solution_record tool do? +

Record an error-solution pair in the solution archive. Associates an error signature (the searchable key), optional full error message, the fix, and related files. Automatically extracts keywords for FTS5 indexing. Side effects: inserts into the solutions table. Use solution_find to check for existing solutions before recording a duplicate. 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 solution_record? +

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

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

Can I rate-limit solution_record? +

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

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

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