VPS_setRootPasswordV1
Set root password for a specified virtual machine. Requirements for password are same as in the [recreate virtual machine endpoint](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines/{virtualMachineId}/recreate). Use this endpoint to update administrator credentials for VPS instances.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-setrootpasswordv1.md
What VPS_setRootPasswordV1 does on Hostinger Api
AI agents use VPS_setRootPasswordV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
password | string | Yes | Root password for the virtual machine |
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_setRootPasswordV1 is rated Medium
This tool modifies the root/administrator password on a VPS instance. It is a Write operation (credential update), but carries high severity because an AI agent misusing it could lock out legitimate users by changing root credentials, effectively causing a denial of access to the entire VPS.
From the tool's definition Set root password for a specified virtual machine... Use this endpoint to update administrator credentials for VPS instances.
Risk signalsHandles credentials or secrets (password) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs VPS_setRootPasswordV1 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_setRootPasswordV1, this is the rule to start with:
VPS_setRootPasswordV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_setRootPasswordV1 call is checked against it from then on.
Questions about VPS_setRootPasswordV1
Set root password for a specified virtual machine. Requirements for password are same as in the [recreate virtual machine endpoint](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines/{virtualMachineId}/recreate). Use this endpoint to update administrator credentials for VPS instances. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
VPS_setRootPasswordV1 accepts 2 parameters: password, virtualMachineId. Required: password, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_setRootPasswordV1: 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.
VPS_setRootPasswordV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the VPS_setRootPasswordV1 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.
Set action: deny in the PolicyLayer policy for VPS_setRootPasswordV1. 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.
VPS_setRootPasswordV1 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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue