VPS_setHostnameV1
Set hostname for a specified virtual machine. Changing hostname does not update PTR record automatically. If you want your virtual machine to be reachable by a hostname, you need to point your domain A/AAAA records to virtual machine IP as well. Use this endpoint to configure custom hostnames for...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-sethostnamev1.md
What VPS_setHostnameV1 does on Hostinger Api
AI agents use VPS_setHostnameV1 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 |
|---|---|---|---|
hostname | string | Yes | hostname parameter |
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_setHostnameV1 is rated Medium
This tool modifies VPS configuration by setting a hostname, which is a Write operation (creates or modifies data reversibly). While hostname changes can affect network behavior and services relying on hostname resolution, the change itself is reversible and does not cause data loss or financial transactions.
From the tool's definition Tool name 'VPS_setHostnameV1' and description 'Set hostname for a specified virtual machine' indicate a modification operation. The description explicitly states this configures custom hostnames, which is a reversible change to VPS configuration.
Risk signalsAccepts URL/endpoint input (hostname)
Attacks that exploit this kind of access
The rule that runs VPS_setHostnameV1 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_setHostnameV1, this is the rule to start with:
VPS_setHostnameV1 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_setHostnameV1 call is checked against it from then on.
Questions about VPS_setHostnameV1
Set hostname for a specified virtual machine. Changing hostname does not update PTR record automatically. If you want your virtual machine to be reachable by a hostname, you need to point your domain A/AAAA records to virtual machine IP as well. Use this endpoint to configure custom hostnames 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_setHostnameV1 accepts 2 parameters: hostname, virtualMachineId. Required: hostname, 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_setHostnameV1: 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_setHostnameV1 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_setHostnameV1 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_setHostnameV1. 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_setHostnameV1 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