execute_command_in_container

THE RISK

High Risk

Why execute_command_in_container needs a policy

This tool executes arbitrary commands within a containerized environment. While the Docker sandbox provides isolation, an AI agent with access to this tool could execute any command supported by the container runtime, potentially exfiltrating data, modifying container state, or performing other operations whose effects depend entirely on the command argument.

From the tool's definition Tool name 'execute_command_in_container' and description 'Runs commands in a container' directly indicate code/command execution capability.

Documented attack patterns abuse exactly the kind of access execute_command_in_container gives an agent:

POLICY

How to control execute_command_in_container

PolicyLayer is an MCP gateway — it sits between your AI agents and Sandbox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_command_in_container:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_command_in_container": {
      "limits": [
        {
          "counter": "execute_command_in_container_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Sandbox MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sandbox MCP Server tools

Destructive exit_container closes a container to cleanup environment when finished Execute create_container_environment Creates a new Docker container with specified image Write create_file_in_container Creates a file in a container Write export_dockerfile exports a docker file to create a persistant environment Write save_container_state Saves the container state to a persistent container

All 6 Sandbox MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Sandbox MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_command_in_container

What does the execute_command_in_container tool do? +

Runs commands in a container. It is categorised as a Execute tool in the Sandbox MCP Server 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_command_in_container? +

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

What risk level is execute_command_in_container? +

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

Can I rate-limit execute_command_in_container? +

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

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

execute_command_in_container is provided by the Sandbox MCP Server MCP server (tsuchijo/sandbox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sandbox MCP Server tool call.

Start from Sandbox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →