record_filter_pattern · Claude Session Continuity MCP

WHAT IT DOES

What record_filter_pattern does on Claude Session Continuity

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

This tool writes/stores filter pattern data for future reference. It creates a record of API content filtering events to help avoid similar situations. This is a Write operation with low severity since it only logs metadata about filtering events rather than modifying critical data or executing code. Confidence is slightly reduced because the description is in Korean and the exact storage mechanism is unclear.

From the tool's definition '기록합니다' (records/logs) and '패턴을 기록' (record a pattern) — stores API content filtering patterns that were triggered, to be used for avoidance in similar situations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_filter_pattern Rate-limited

record_filter_pattern 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_filter_pattern": {
      "limits": [
        {
          "counter": "record_filter_pattern_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_filter_pattern

What does the record_filter_pattern tool do? +

API content filtering에 걸린 패턴을 기록합니다. 비슷한 상황 회피에 사용됩니다. 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_filter_pattern? +

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

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

Can I rate-limit record_filter_pattern? +

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

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

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