vps_start

Start a virtual machine.

SERVERHostinger SOURCEidugeni/hostinger-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/vps-start.md

WHAT IT DOES

What vps_start does on Hostinger

AI agents invoke vps_start to trigger actions in Hostinger. 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 vps_start is rated High

Initiating VM infrastructure is an Execute action: it runs/triggers an operation on external systems with real-world consequences (resource allocation, potential service disruption or availability). While not destructive (the VM isn't deleted) or financial (no money moves), it is a consequential state change.

From the tool's definition 'Start a virtual machine' — this tool triggers an external operation (VM startup) whose effects are irreversible within a session and depend on which VM is targeted as an argument.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vps_start safely

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

vps_start Rate-limited

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

FAQ

Questions about vps_start

What does the vps_start tool do? +

Start a virtual machine. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vps_start? +

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

What risk level is vps_start? +

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

Can I rate-limit vps_start? +

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

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

vps_start is provided by the Hostinger MCP server (idugeni/hostinger-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, and thousands of servers like it.

This server

All 284 Hostinger tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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