shell_exec · Mcpx MCP: Risk & Policy

WHAT IT DOES

What shell_exec does on Mcpx

AI agents invoke shell_exec to trigger actions in Mcpx. 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 shell_exec needs a policy

Despite the empty description, the tool name 'shell_exec' strongly implies arbitrary shell command execution. In the context of a server explicitly designed for 'complete shell and SSH mastery' and 'command execution', this tool almost certainly executes shell commands.

From the tool's definition Tool name 'shell_exec' on a server described as enabling 'command execution, interactive sessions' with 'auditing and policy controls'; sibling tools include 'shell_script' and 'shell_spawn' confirming shell execution context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shell_exec Rate-limited

shell_exec 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": {
    "shell_exec": {
      "limits": [
        {
          "counter": "shell_exec_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 Mcpx, so you can run agents against it safely.

FAQ

Questions about shell_exec

What does the shell_exec tool do? +

shell_exec. It is categorised as a Execute tool in the Mcpx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on shell_exec? +

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

What risk level is shell_exec? +

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

Can I rate-limit shell_exec? +

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

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

shell_exec is provided by the Mcpx MCP server (rmednitzer/relay-shell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.