sandbox_ssh_disable
Close the SSH forward (port 22) of a sandbox. The key stays injected and sshd keeps running inside the box — it just becomes unreachable from outside. To actually revoke someone, remove their key from /app/secrets.env.
This record as markdown: /tools/cloud-easybits-easybits/sandbox-ssh-disable.md
What sandbox_ssh_disable does on EasyBits
AI agents use sandbox_ssh_disable 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_ssh_disable is rated Medium
Disables external SSH access reversibly by closing port forwarding; modifiable not destructive.
From the tool's definition Close the SSH forward (port 22) of a sandbox; reversible network access modification.
Attacks that exploit this kind of access
The rule that runs sandbox_ssh_disable 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_disable, this is the rule to start with:
sandbox_ssh_disable 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_ssh_disable call is checked against it from then on.
Questions about sandbox_ssh_disable
Close the SSH forward (port 22) of a sandbox. The key stays injected and sshd keeps running inside the box — it just becomes unreachable from outside. To actually revoke someone, remove their key from /app/secrets.env. 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_ssh_disable: 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_disable 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_ssh_disable 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_disable. 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_disable 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