claude_execute

Execute a task using Claude Code on the remote PC. Spawns Claude CLI with full coding capabilities (read/write files, run commands, git ops). Returns structured JSON output.

SERVERClaude Bridge SOURCE0motionguy/claude-bridge-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0motionguy-claude-bridge-mcp/claude-execute.md

WHAT IT DOES

What claude_execute does on Claude Bridge

AI agents invoke claude_execute to trigger actions in Claude Bridge. 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.

RISK

Why claude_execute is rated High

This tool executes arbitrary tasks on a remote machine via Claude Code CLI, with capabilities spanning file operations, shell command execution, and git operations. While the tool itself supports write/read operations, the primary risk is the 'run commands' capability, which allows execution of arbitrary code whose effects depend entirely on the arguments provided. This falls into the Execute category.

From the tool's definition Tool description states: 'Spawns Claude CLI with full coding capabilities (read/write files, run commands, git ops)' and 'Execute a task using Claude Code on the remote PC.' The explicit mention of 'run commands' and 'full coding capabilities' on a remote PC…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claude_execute safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claude_execute, this is the rule to start with:

claude_execute Rate-limited

claude_execute 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": {
    "claude_execute": {
      "limits": [
        {
          "counter": "claude_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Bridge, apply this rule, and every claude_execute call is checked against it from then on.

FAQ

Questions about claude_execute

What does the claude_execute tool do? +

Execute a task using Claude Code on the remote PC. Spawns Claude CLI with full coding capabilities (read/write files, run commands, git ops). Returns structured JSON output. It is categorised as a Execute tool in the Claude Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on claude_execute? +

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

What risk level is claude_execute? +

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

Can I rate-limit claude_execute? +

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

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

claude_execute is provided by the Claude Bridge MCP server (0motionguy/claude-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Bridge, and thousands of servers like it.

This server

All 4 Claude Bridge tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →