VPS_getTemplatesV1

Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances.

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-gettemplatesv1.md

WHAT IT DOES

What VPS_getTemplatesV1 does on Hostinger Api

AI agents call VPS_getTemplatesV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why VPS_getTemplatesV1 is rated Low

This tool retrieves a list of available OS templates for VPS instances without modifying any data, creating side effects, or executing code. It is purely informational, used to list options before taking other actions. The blast radius of misuse is minimal—an attacker could only gather information about available templates. No data is modified, deleted, or financial operations are performed.

From the tool's definition The tool name contains 'get' and the description states 'Retrieve available OS templates' without modification capabilities. This is a read operation that queries available data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_getTemplatesV1 Allowed

VPS_getTemplatesV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "VPS_getTemplatesV1": {}
  }
}

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

FAQ

Questions about VPS_getTemplatesV1

What does the VPS_getTemplatesV1 tool do? +

Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on VPS_getTemplatesV1? +

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

VPS_getTemplatesV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit VPS_getTemplatesV1? +

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

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

VPS_getTemplatesV1 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 255 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →