sandbox_initialize · Node Code Sandbox MCP: Risk & Policy

WHAT IT DOES

What sandbox_initialize does on Node Code Sandbox MCP

AI agents invoke sandbox_initialize to trigger actions in Node Code Sandbox 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 sandbox_initialize needs a policy

This tool executes infrastructure-level operations (Docker container initialization) and enables arbitrary code execution downstream. While the sandbox is designed for isolation, the ability to initialize containers is an Execute action—it triggers external operations whose side effects are not reversible without additional teardown actions.

From the tool's definition Starts a new isolated Docker container running Node.js — instantiates external infrastructure and initiates a computing environment whose behavior depends on subsequent commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sandbox_initialize Rate-limited

sandbox_initialize 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": {
    "sandbox_initialize": {
      "limits": [
        {
          "counter": "sandbox_initialize_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 Node Code Sandbox MCP, so you can run agents against it safely.

FAQ

Questions about sandbox_initialize

What does the sandbox_initialize tool do? +

Start a new isolated Docker container running Node.js. Used to set up a sandbox session for multiple commands and scripts. It is categorised as a Execute tool in the Node Code Sandbox 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 sandbox_initialize? +

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

What risk level is sandbox_initialize? +

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

Can I rate-limit sandbox_initialize? +

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

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

sandbox_initialize is provided by the Node Code Sandbox MCP server (mozicim/node-code-sandbox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.