record_solution · Claude Session Continuity MCP

WHAT IT DOES

What record_solution does on Claude Session Continuity

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

This tool writes/stores error solution records for future reference. It creates new data (solution entries) in the session continuity system. The description is in Korean and non-English, slightly lowering confidence, but the semantics are clear: it persists a record of how an error was resolved. No deletion, execution, or financial action is implied. Severity is low since it only writes metadata/context records.

From the tool's definition '에러 해결 방법을 기록합니다' (Records error resolution methods) and '나중에 같은 에러 시 참조 가능' (can be referenced later for the same error) — creates/stores a solution record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_solution Rate-limited

record_solution 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": {
    "record_solution": {
      "limits": [
        {
          "counter": "record_solution_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 record_solution

What does the record_solution tool do? +

에러 해결 방법을 기록합니다. 에러 해결 후 호출하면 나중에 같은 에러 시 참조 가능. 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 record_solution? +

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

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

Can I rate-limit record_solution? +

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

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

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