run_verification · Claude Session Continuity MCP

WHAT IT DOES

What run_verification does on Claude Session Continuity

AI agents invoke run_verification to trigger actions in Claude Session Continuity. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_verification needs a policy

This tool executes build processes, test suites, and linting operations—external operations whose effects depend on the project state and configuration. While not destructive by itself, executing build/test/lint commands can have side effects (file generation, temporary artifacts, resource consumption, and potential compilation/runtime errors).

From the tool's definition Tool description states '프로젝트의 빌드/테스트/린트를 한 번에 실행하고 결과를 반환합니다' which translates to 'runs project build/test/lint all at once and returns results'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_verification Rate-limited

run_verification stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_verification": {
      "limits": [
        {
          "counter": "run_verification_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_verification

What does the run_verification tool do? +

프로젝트의 빌드/테스트/린트를 한 번에 실행하고 결과를 반환합니다. It is categorised as a Execute tool in the Claude Session Continuity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_verification? +

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

run_verification is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_verification? +

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

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

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