run_command

Execute a shell command in a secure sandboxed environment with risk analysis, timeout enforcement, and output capture. Commands are analyzed for safety before execution.

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/run-command.md

WHAT IT DOES

What run_command does on Terminal Guardian

AI agents invoke run_command to trigger actions in Terminal Guardian. 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 run_command is rated High

This tool executes arbitrary shell commands, which is the defining characteristic of the Execute category. While sandboxing and pre-execution analysis reduce blast radius compared to unsandboxed execution, the fundamental capability to run external code/commands with effects dependent on the command arguments places it in Execute.

From the tool's definition Tool name 'run_command' combined with description stating it 'Execute[s] a shell command' and 'output capture' confirms this is a command execution tool. The presence of risk analysis and sandboxing are mitigations, not category changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_command safely

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

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.

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

FAQ

Questions about run_command

What does the run_command tool do? +

Execute a shell command in a secure sandboxed environment with risk analysis, timeout enforcement, and output capture. Commands are analyzed for safety before execution. It is categorised as a Execute tool in the Terminal Guardian 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 Terminal Guardian 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 Terminal Guardian. 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 Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Terminal Guardian, and thousands of servers like it.

This server

All 25 Terminal Guardian tools → High-risk tools on this server →

Across the catalogue

run on 0sec →adb_shell_command on Android Forensics ADB MCP Server →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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