deploy_machine

Publish the machine

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

WHAT IT DOES

What deploy_machine does on EasyBits

AI agents invoke deploy_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 deploy_machine is rated High

Deploys persistent microVMs with root access and internet connectivity, enabling arbitrary code execution via agents.

From the tool's definition Publish the machine; root, internet access, persistent VMs

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deploy_machine Rate-limited

deploy_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": {
    "deploy_machine": {
      "limits": [
        {
          "counter": "deploy_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 deploy_machine call is checked against it from then on.

FAQ

Questions about deploy_machine

What does the deploy_machine tool do? +

Publish the machine. 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 deploy_machine? +

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

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

Can I rate-limit deploy_machine? +

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

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

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