VPS_startProjectV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 22 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-startprojectv1.md

WHAT IT DOES

What VPS_startProjectV1 does on Hostinger Api

AI agents invoke VPS_startProjectV1 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
`projectName`	string	Yes	Docker Compose project name using alphanumeric characters, dashes, and underscores only
`virtualMachineId`	integer	Yes	Virtual Machine ID

Parameters from the server's own tool schema.

RISK

Why VPS_startProjectV1 is rated High

This tool executes a Docker Compose operation that starts services/containers. While not destructive and not creating permanent data changes, it triggers external computational operations whose side effects depend on the configuration and nature of the services being started. This falls under Execute category as it runs operations whose consequences are determined by arguments and external state.

From the tool's definition Starts all services in a Docker Compose project, brings up containers in dependency order. This triggers external operations (container startup) whose effects depend on which services are defined in the project.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_startProjectV1 Rate-limited

VPS_startProjectV1 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_startProjectV1": {
      "limits": [
        {
          "counter": "vps_startprojectv1_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_startProjectV1 call is checked against it from then on.

FAQ

Questions about VPS_startProjectV1

What does the VPS_startProjectV1 tool do? +

Starts all services in a Docker Compose project that are currently stopped. This operation brings up containers in the correct dependency order as defined in the compose file. Use this to resume a project that was previously stopped or to start services after a system reboot. 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_startProjectV1 accept? +

VPS_startProjectV1 accepts 2 parameters: projectName, virtualMachineId. Required: projectName, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_startProjectV1? +

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

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

Can I rate-limit VPS_startProjectV1? +

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

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

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