sandbox_keepalive
Toggle KEEP-ALIVE on the user's session sandbox — the chat twin of the ◉ keep-alive control in the SANDBOX pane. on: true holds the sandbox up across idle periods (so it doesn't wind down between uses) until turned off or the daily keep-alive clock runs out; on: false returns it to the standard f...
This record as markdown: /tools/ai-rokha-rokha/sandbox-keepalive.md
What sandbox_keepalive does on Rokha
AI agents call sandbox_keepalive 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 |
|---|---|---|---|
on | boolean | — | true = keep the sandbox alive across idle (default); false = let it wind down on the normal idle window. |
wallet_address | string | Yes |
Parameters from the server's own tool schema.
Why sandbox_keepalive is rated Low
Even though sandbox_keepalive only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sandbox_keepalive 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_keepalive, this is the rule to start with:
sandbox_keepalive is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every sandbox_keepalive call is checked against it from then on.
Questions about sandbox_keepalive
Toggle KEEP-ALIVE on the user's session sandbox — the chat twin of the ◉ keep-alive control in the SANDBOX pane. on: true holds the sandbox up across idle periods (so it doesn't wind down between uses) until turned off or the daily keep-alive clock runs out; on: false returns it to the standard free idle window (which shuts it down on inactivity). USE THIS when the user asks to keep their sandbox alive / warm / persistent / from timing out, or to stop keeping it alive. Keep-alive spends a per-ACCOUNT daily clock (paid plans only — Casual 6h / Builder 12h / Pro 24h; banked Sandbox Time top-ups extend it), so an anonymous caller is told to log in. Needs wallet_address. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
sandbox_keepalive accepts 2 parameters: on, wallet_address. Required: wallet_address. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for sandbox_keepalive: 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.
sandbox_keepalive is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sandbox_keepalive 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.
Set action: deny in the PolicyLayer policy for sandbox_keepalive. 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.
sandbox_keepalive 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.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue