sandbox_set_idle
Change the idle policy of an EXISTING sandbox. suspendOnIdle=true: when the TTL elapses the box is SUSPENDED (snapshot, resume ~1s, state kept) instead of destroyed; idleTtlSeconds re-arms the idle clock from now; hardTtlSeconds (optional) is the deadline after which it is destroyed even while as...
This record as markdown: /tools/cloud-easybits-easybits/sandbox-set-idle.md
What sandbox_set_idle does on EasyBits
AI agents use sandbox_set_idle to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why sandbox_set_idle is rated Medium
Modifies sandbox configuration reversibly; no data destruction or code execution.
From the tool's definition Change the idle policy of an EXISTING sandbox
Attacks that exploit this kind of access
The rule that runs sandbox_set_idle 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_set_idle, this is the rule to start with:
sandbox_set_idle stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_set_idle call is checked against it from then on.
Questions about sandbox_set_idle
Change the idle policy of an EXISTING sandbox. suspendOnIdle=true: when the TTL elapses the box is SUSPENDED (snapshot, resume ~1s, state kept) instead of destroyed; idleTtlSeconds re-arms the idle clock from now; hardTtlSeconds (optional) is the deadline after which it is destroyed even while asleep. Use it for long-lived sessions that must survive quiet periods (an agent between turns). suspendOnIdle=false returns it to the ephemeral scheme (409 if the TTL already elapsed — extend first). It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_set_idle: 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.
sandbox_set_idle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sandbox_set_idle 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_set_idle. 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_set_idle 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.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue