VPS_setupPurchasedVirtualMachineV1

Setup newly purchased virtual machine with initial state. Use this endpoint to configure and initialize purchased VPS instances.

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 113 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-setuppurchasedvirtualmachinev1.md

WHAT IT DOES

What VPS_setupPurchasedVirtualMachineV1 does on Hostinger Api

AI agents invoke VPS_setupPurchasedVirtualMachineV1 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
`ns1`	string	—	Name server 1
`ns2`	string	—	Name server 2
`hostname`	string	—	Override default hostname of the virtual machine
`password`	string	—	Password for the virtual machine. If not provided, random password will be generated. Password will not be shown in the response.
`public_key`	object	—	Use SSH key
`template_id`	integer	Yes	Template ID
`data_center_id`	integer	Yes	Data center ID
`enable_backups`	boolean	—	Enable weekly backup schedule
`install_monarx`	boolean	—	Install Monarx malware scanner (if supported)
`virtualMachineId`	integer	Yes	Virtual Machine ID
`post_install_script_id`	integer	—	Post-install script ID

Parameters from the server's own tool schema.

RISK

Why VPS_setupPurchasedVirtualMachineV1 is rated High

This tool configures and initializes a VPS instance, triggering external infrastructure operations (provisioning, setup) on a remote server. It is not merely writing data but executing an initialization/configuration process on a live system. Misuse could result in misconfigured or unintended VPS deployments, making it high severity.

From the tool's definition Setup newly purchased virtual machine with `initial` state. Use this endpoint to configure and initialize purchased VPS instances.

Risk signalsAccepts URL/endpoint input (hostname) · Handles credentials or secrets (password) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_setupPurchasedVirtualMachineV1 Rate-limited

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

FAQ

Questions about VPS_setupPurchasedVirtualMachineV1

What does the VPS_setupPurchasedVirtualMachineV1 tool do? +

Setup newly purchased virtual machine with initial state. Use this endpoint to configure and initialize purchased 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_setupPurchasedVirtualMachineV1 accept? +

VPS_setupPurchasedVirtualMachineV1 accepts 11 parameters: ns1, ns2, hostname, password, public_key, template_id, data_center_id, enable_backups, install_monarx, virtualMachineId, post_install_script_id. Required: template_id, data_center_id, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_setupPurchasedVirtualMachineV1? +

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

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

Can I rate-limit VPS_setupPurchasedVirtualMachineV1? +

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

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

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