sandbox_run_cell

Run code in the sandbox

SERVEREasyBits SOURCE@easybits.cloud/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-run-cell.md

WHAT IT DOES

What sandbox_run_cell does on EasyBits

AI agents invoke sandbox_run_cell to trigger actions in EasyBits. 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 sandbox_run_cell is rated High

Executes arbitrary code with root privileges and network access; highest impact abuse potential.

From the tool's definition Run code in the sandbox with persistent Linux microVMs, root access, internet.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_run_cell safely

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

sandbox_run_cell Rate-limited

sandbox_run_cell 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_run_cell": {
      "limits": [
        {
          "counter": "sandbox_run_cell_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 EasyBits, apply this rule, and every sandbox_run_cell call is checked against it from then on.

FAQ

Questions about sandbox_run_cell

What does the sandbox_run_cell tool do? +

Run code in the sandbox. It is categorised as a Execute tool in the EasyBits 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_run_cell? +

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

What risk level is sandbox_run_cell? +

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

Can I rate-limit sandbox_run_cell? +

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

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

sandbox_run_cell is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →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 →