redeploy_machine
Build a BRAND NEW machine from a release: provisions a box, unpacks the code, builds and starts it. Two jobs, one path — recovering a machine that died, and CHANGING TIER (there is no in-place resize: you recreate at the new tier). Pass replaceSandboxId to release the old machine once the new one...
This record as markdown: /tools/cloud-easybits-easybits/redeploy-machine.md
What redeploy_machine does on EasyBits
AI agents invoke redeploy_machine 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 redeploy_machine is rated High
Triggers external infrastructure operations whose effects depend on arguments; recreates machines with significant resource implications.
From the tool's definition provisions a box, unpacks code, builds and starts it, recreate at new tier
Attacks that exploit this kind of access
The rule that runs redeploy_machine 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 redeploy_machine, this is the rule to start with:
redeploy_machine 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 redeploy_machine call is checked against it from then on.
Questions about redeploy_machine
Build a BRAND NEW machine from a release: provisions a box, unpacks the code, builds and starts it. Two jobs, one path — recovering a machine that died, and CHANGING TIER (there is no in-place resize: you recreate at the new tier). Pass replaceSandboxId to release the old machine once the new one is confirmed running, or you pay for both. The new box starts with NO data — restore a backup after. 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 redeploy_machine: 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.
redeploy_machine 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 redeploy_machine 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 redeploy_machine. 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.
redeploy_machine 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