Sandbox
sandbox: 17 operations.
Also for this capability: API · CLI · MCP · SDKs
sandbox: 17 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | sandbox |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | POST /v1/sandbox/end · GET /v1/sandbox/{id} · POST /v1/sandbox/lease · POST /v1/sandbox/read · POST /v1/sandbox/run · POST /v1/sandbox/stop · POST /v1/sandbox/write |
| Product | sandbox |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "sandbox",
"arguments": {
"op": "list_sandboxes"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
sandbox dispatches to 17 operations. 7 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
end_sandbox | POST /v1/sandbox/end | sandbox | End a sandbox and release it |
get_sandbox_by_id | GET /v1/sandbox/{id} | sandbox | Returns one sandbox: its class, project, image, the runtime it was given, its status and when its lease ends. |
lease_sandbox | POST /v1/sandbox/lease | sandbox | Lease a sandbox — a real computer — or resume one you hold |
read_sandbox_file | POST /v1/sandbox/read | sandbox | Read a file from a sandbox you hold |
run_in_sandbox | POST /v1/sandbox/run | sandbox | Run a command in a sandbox you hold and read its output |
stop_run | POST /v1/sandbox/stop | sandbox | Stop what a sandbox is running, and keep the sandbox |
write_sandbox_file | POST /v1/sandbox/write | sandbox | Write a file into a sandbox you hold |
The same capability over plain HTTP is in the sandbox API reference, on https://api.hanzo.ai.
All 120 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.