VPS_setNameserversV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 42 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-setnameserversv1.md

WHAT IT DOES

What VPS_setNameserversV1 does on Hostinger Api

AI agents use VPS_setNameserversV1 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
`ns1`	string	Yes	ns1 parameter
`ns2`	string	—	ns2 parameter
`ns3`	string	—	ns3 parameter
`virtualMachineId`	integer	Yes	Virtual Machine ID

Parameters from the server's own tool schema.

RISK

Why VPS_setNameserversV1 is rated Medium

This tool creates or modifies VPS nameserver settings, which is a configuration change that can be reverted (e.g., by setting different nameservers or restoring defaults). It does not delete data or execute arbitrary code, but misconfiguration could cause service disruption. Categorized as Write rather than Execute because it modifies a specific configuration parameter rather than executing arbitrary operations.

From the tool's definition Tool description states 'Set nameservers for a specified virtual machine' and 'configure custom DNS resolvers for VPS instances.' This modifies VPS DNS configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_setNameserversV1 Rate-limited

VPS_setNameserversV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "VPS_setNameserversV1": {
      "limits": [
        {
          "counter": "vps_setnameserversv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_setNameserversV1 call is checked against it from then on.

FAQ

Questions about VPS_setNameserversV1

What does the VPS_setNameserversV1 tool do? +

Set nameservers for a specified virtual machine. Be aware, that improper nameserver configuration can lead to the virtual machine being unable to resolve domain names. Use this endpoint to configure custom DNS resolvers 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.

What parameters does VPS_setNameserversV1 accept? +

VPS_setNameserversV1 accepts 4 parameters: ns1, ns2, ns3, virtualMachineId. Required: ns1, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_setNameserversV1? +

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

VPS_setNameserversV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit VPS_setNameserversV1? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →