sandbox_ssh_enable
Give the user SSH into the box, in one call: injects their public key(s) and restarts the box sshd. HAND THE USER
This record as markdown: /tools/cloud-easybits-easybits/sandbox-ssh-enable.md
What sandbox_ssh_enable does on EasyBits
AI agents invoke sandbox_ssh_enable to trigger actions in EasyBits. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why sandbox_ssh_enable is rated High
Enables SSH access by injecting keys and restarting sshd, granting persistent remote execution capability.
From the tool's definition injects their public key(s) and restarts the box sshd
Attacks that exploit this kind of access
The rule that runs sandbox_ssh_enable 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_ssh_enable, this is the rule to start with:
sandbox_ssh_enable stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_ssh_enable call is checked against it from then on.
Questions about sandbox_ssh_enable
Give the user SSH into the box, in one call: injects their public key(s) and restarts the box sshd. HAND THE USER. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_ssh_enable: 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_ssh_enable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sandbox_ssh_enable 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_ssh_enable. 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_ssh_enable 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.
Across the catalogue