create_machine

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What create_machine does on EasyBits

AI agents use create_machine to commit financial operations through EasyBits, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why create_machine is rated Critical

Directly commits financial obligations by purchasing a recurring-billing VM subscription.

From the tool's definition Buy an ALWAYS-ON machine, flat MXN/month, hosting bills on its own

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_machine Approval-gated

Any call to create_machine is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_machine": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about create_machine

What does the create_machine tool do? +

Buy an ALWAYS-ON machine (permanent VM, flat MXN/month). NO platform plan needed — hosting bills on its own. If the account has an active plan the machine is provisioned right away and rides that invoice; otherwise this returns { checkoutUrl } for the customer to pay, and the machine is provisioned automatically once payment clears (poll list_machines). Reserved CPU and performance-4x are by-request until enabled. It is categorised as a Financial tool in the EasyBits MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on create_machine? +

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

create_machine is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit create_machine? +

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

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

create_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 → Critical-risk tools on this server →

Across the catalogue

fundos_create_capital_call on Fundos →create_payment on Shopmonkey MCP Server →create_agent on Conviction →bank_transaction_create on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →