sandbox_exec_status

Poll a background command started with sandbox_exec_background. Returns status (running/exited), exitCode (when exited), and the captured stdout/stderr tail (last 1MB each).

SERVEREasyBits SOURCE@easybits.cloud/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-exec-status.md

WHAT IT DOES

What sandbox_exec_status does on EasyBits

AI agents call sandbox_exec_status to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sandbox_exec_status is rated Low

Polls execution status and retrieves output; no side effects or command execution.

From the tool's definition Poll background command status, exitCode, stdout/stderr tail.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_exec_status 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_exec_status, this is the rule to start with:

sandbox_exec_status Allowed

sandbox_exec_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sandbox_exec_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sandbox_exec_status

What does the sandbox_exec_status tool do? +

Poll a background command started with sandbox_exec_background. Returns status (running/exited), exitCode (when exited), and the captured stdout/stderr tail (last 1MB each). It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sandbox_exec_status? +

Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_exec_status: 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_exec_status? +

sandbox_exec_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sandbox_exec_status? +

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

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

sandbox_exec_status 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 →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →