rollback_machine

Put a previous release back on the SAME machine: download, extract and restart. No build: a release published by launch_app ships its build. Use after a bad deploy. Data is untouched.

SERVEREasyBits SOURCE@easybits.cloud/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/rollback-machine.md

WHAT IT DOES

What rollback_machine does on EasyBits

AI agents invoke rollback_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.

RISK

Why rollback_machine is rated High

Triggers external system operations with wide-ranging effects; restarts infrastructure despite data preservation claims.

From the tool's definition download, extract and restart machine; effects depend on release argument

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rollback_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 rollback_machine, this is the rule to start with:

rollback_machine Rate-limited

rollback_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rollback_machine": {
      "limits": [
        {
          "counter": "rollback_machine_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every rollback_machine call is checked against it from then on.

FAQ

Questions about rollback_machine

What does the rollback_machine tool do? +

Put a previous release back on the SAME machine: download, extract and restart. No build: a release published by launch_app ships its build. Use after a bad deploy. Data is untouched. 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.

How do I enforce a policy on rollback_machine? +

Register the EasyBits MCP server in PolicyLayer and add a rule for rollback_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.

What risk level is rollback_machine? +

rollback_machine is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rollback_machine? +

Yes. Add a rate_limit block to the rollback_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.

How do I block rollback_machine completely? +

Set action: deny in the PolicyLayer policy for rollback_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.

What MCP server provides rollback_machine? +

rollback_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.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →