sandbox_status

The user's session-sandbox state (starting | active | ending | ended | none) plus the 20 newest work items (id, kind, status, result). Check this before sandbox_exec, and to report what ran.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/sandbox-status.md

WHAT IT DOES

What sandbox_status does on Rokha

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

Parameter	Type	Required	Description
`wallet_address`	string	Yes

Parameters from the server's own tool schema.

RISK

Why sandbox_status is rated Low

Queries sandbox status and work history without modifying or executing any operations.

From the tool's definition session-sandbox state, work items, check before execution, report

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_status safely

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

sandbox_status Allowed

sandbox_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_status": {}
  }
}

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

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

FAQ

Questions about sandbox_status

What does the sandbox_status tool do? +

The user's session-sandbox state (starting | active | ending | ended | none) plus the 20 newest work items (id, kind, status, result). Check this before sandbox_exec, and to report what ran. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does sandbox_status accept? +

sandbox_status accepts 1 parameter: wallet_address. Required: wallet_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sandbox_status? +

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

What risk level is sandbox_status? +

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

Can I rate-limit sandbox_status? +

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

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

sandbox_status is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha 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 →