run_command · Local Dev Bridge MCP: Risk & Policy

WHAT IT DOES

What run_command does on Local Dev Bridge MCP

AI agents invoke run_command to trigger actions in Local Dev Bridge MCP. 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_command needs a policy

Shell command execution is inherently an Execute category risk because outcomes depend entirely on the command argument provided. An AI agent could execute malicious commands (rm -rf, credential exfiltration, supply chain attacks via npm, lateral movement). Severity is critical because shell access in a development environment can compromise source code, secrets, build systems, and infrastructure.

From the tool's definition Tool description explicitly states 'Execute a shell command' with broad scope including 'npm install, git commands, tests, etc.' The tool accepts arbitrary shell commands in a projects directory context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_command Rate-limited

run_command 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_command": {
      "limits": [
        {
          "counter": "run_command_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 Local Dev Bridge MCP, so you can run agents against it safely.

FAQ

Questions about run_command

What does the run_command tool do? +

Execute a shell command in the projects directory. Use for running npm install, git commands, tests, etc. It is categorised as a Execute tool in the Local Dev Bridge MCP 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_command? +

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

What risk level is run_command? +

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

Can I rate-limit run_command? +

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

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

run_command is provided by the Local Dev Bridge MCP server (talentedmrweb/local-dev-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.