VPS_startVirtualMachineV1

Start a specified virtual machine. If the virtual machine is already running, the request will still be processed without any effect. Use this endpoint to power on stopped VPS instances.

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-startvirtualmachinev1.md

WHAT IT DOES

What VPS_startVirtualMachineV1 does on Hostinger Api

AI agents invoke VPS_startVirtualMachineV1 to trigger actions in Hostinger Api. 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.

Parameter	Type	Required	Description
`virtualMachineId`	integer	Yes	Virtual Machine ID

Parameters from the server's own tool schema.

RISK

Why VPS_startVirtualMachineV1 is rated High

This tool executes a command to power on a VPS instance, which is an irreversible operational action with real infrastructure consequences. While not destructive (data is not deleted), it changes system state and could disrupt services if misused by an AI agent. Classified as Execute rather than Write because it triggers external infrastructure operations whose effects depend on which VM is targeted.

From the tool's definition Tool directly triggers an external operation: 'Start a specified virtual machine' and 'power on stopped VPS instances'. These are state-changing actions on infrastructure that execute immediately based on provided arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs VPS_startVirtualMachineV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For VPS_startVirtualMachineV1, this is the rule to start with:

VPS_startVirtualMachineV1 Rate-limited

VPS_startVirtualMachineV1 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": {
    "VPS_startVirtualMachineV1": {
      "limits": [
        {
          "counter": "vps_startvirtualmachinev1_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 Hostinger Api, apply this rule, and every VPS_startVirtualMachineV1 call is checked against it from then on.

FAQ

Questions about VPS_startVirtualMachineV1

What does the VPS_startVirtualMachineV1 tool do? +

Start a specified virtual machine. If the virtual machine is already running, the request will still be processed without any effect. Use this endpoint to power on stopped VPS instances. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does VPS_startVirtualMachineV1 accept? +

VPS_startVirtualMachineV1 accepts 1 parameter: virtualMachineId. Required: virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_startVirtualMachineV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_startVirtualMachineV1: 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 Hostinger Api. Nothing to install.

What risk level is VPS_startVirtualMachineV1? +

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

Can I rate-limit VPS_startVirtualMachineV1? +

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

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

VPS_startVirtualMachineV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api 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 →