VPS_stopVirtualMachineV1

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-stopvirtualmachinev1.md

WHAT IT DOES

What VPS_stopVirtualMachineV1 does on Hostinger Api

AI agents invoke VPS_stopVirtualMachineV1 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_stopVirtualMachineV1 is rated High

This tool executes a power state change on infrastructure, which is an irreversible operational action that disrupts service availability. Although the description clarifies this does not delete data, stopping a VM is a consequential Execute action (not Destructive because the VM and its data persist; not Write because it's not data modification).

From the tool's definition Tool description states 'Stop a specified virtual machine' and 'power off running VPS instances' — this triggers an external operation (VM shutdown) whose effects depend on which VM is targeted.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_stopVirtualMachineV1 Rate-limited

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

FAQ

Questions about VPS_stopVirtualMachineV1

What does the VPS_stopVirtualMachineV1 tool do? +

Stop a specified virtual machine. If the virtual machine is already stopped, the request will still be processed without any effect. This is a compute-only power state change and does not affect billing. To stop future charges, disable auto-renewal on the owning subscription. Use this endpoint to power off running 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_stopVirtualMachineV1 accept? +

VPS_stopVirtualMachineV1 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_stopVirtualMachineV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_stopVirtualMachineV1: 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_stopVirtualMachineV1? +

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

Can I rate-limit VPS_stopVirtualMachineV1? +

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

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

VPS_stopVirtualMachineV1 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 382 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 →