test_claude_cli · MCP Claude Context Continuity MCP

WHAT IT DOES

What test_claude_cli does on MCP Claude Context Continuity

AI agents invoke test_claude_cli to trigger actions in MCP Claude Context 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 test_claude_cli needs a policy

This tool executes the Claude CLI to test its configuration. Running an external CLI process is an Execute-category action, as it triggers external operations. Severity is medium because it is a test/validation action but still involves spawning external processes, which could have unintended side effects depending on what the CLI does during the test.

From the tool's definition Tool name 'test_claude_cli' and description 'Claude CLIが正しく設定されているかテスト' (meaning: Test if Claude CLI is correctly configured) — runs a CLI invocation to verify configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_claude_cli Rate-limited

test_claude_cli 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": {
    "test_claude_cli": {
      "limits": [
        {
          "counter": "test_claude_cli_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 MCP Claude Context Continuity, so you can run agents against it safely.

FAQ

Questions about test_claude_cli

What does the test_claude_cli tool do? +

Claude CLIが正しく設定されているかテスト. It is categorised as a Execute tool in the MCP Claude Context 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 test_claude_cli? +

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

What risk level is test_claude_cli? +

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

Can I rate-limit test_claude_cli? +

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

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

test_claude_cli is provided by the MCP Claude Context Continuity MCP server (tethiro/mcp-claude-context-continuity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.