restore_machine

SERVEREasyBits SOURCE@easybits.cloud/mcp

Medium RISK CLASS

Category Write

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/restore-machine.md

WHAT IT DOES

What restore_machine does on EasyBits

AI agents use restore_machine 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.

RISK

Why restore_machine is rated Medium

Modifies machine state and billing reversibly; requires owner authorization but affects subscriptions and resource allocation.

From the tool's definition Revive suspended machine, resume VM, re-attach billing, owner-only

Attacks that exploit this kind of access

RECOMMENDED RULE

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

restore_machine Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore_machine": {
      "limits": [
        {
          "counter": "restore_machine_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about restore_machine

What does the restore_machine tool do? +

Revive a machine that was suspended because its SUBSCRIPTION was cancelled (trial ended, card failed) — it sleeps for 7 days before being purged. Resumes the VM (data intact) and re-attaches billing. Owner-only. Does NOT apply to release_machine, which destroys immediately: for that, restore_machine_from_backup onto a new machine. 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.

How do I enforce a policy on restore_machine? +

Register the EasyBits MCP server in PolicyLayer and add a rule for restore_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 restore_machine? +

restore_machine is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore_machine? +

Yes. Add a rate_limit block to the restore_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 restore_machine completely? +

Set action: deny in the PolicyLayer policy for restore_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 restore_machine? +

restore_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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →