execute_claude_with_context

WHAT IT DOES

What execute_claude_with_context does on MCP Claude Context Continuity

AI agents invoke execute_claude_with_context 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 execute_claude_with_context needs a policy

This tool triggers execution of the Claude CLI with potentially user-controlled file context arguments. This is an Execute category tool because it runs external code/processes whose effects depend on the arguments passed (the context provided). While not inherently destructive, misuse could lead to unintended CLI behaviors or context leakage.

From the tool's definition Tool name contains 'execute_claude' and description indicates it runs Claude CLI ('Claude CLIを実行' = 'execute Claude CLI'). Sibling tools include 'execute_claude' confirming this server executes external processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_claude_with_context Rate-limited

execute_claude_with_context 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": {
    "execute_claude_with_context": {
      "limits": [
        {
          "counter": "execute_claude_with_context_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 execute_claude_with_context

What does the execute_claude_with_context 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 execute_claude_with_context? +

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

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

Can I rate-limit execute_claude_with_context? +

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

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

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