VPS_createNewProjectV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 43 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-createnewprojectv1.md

WHAT IT DOES

What VPS_createNewProjectV1 does on Hostinger Api

AI agents invoke VPS_createNewProjectV1 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
`content`	string	Yes	URL pointing to docker-compose.yaml file, Github repository or raw YAML content of the compose file
`environment`	string	—	Project environment variables
`project_name`	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_createNewProjectV1 is rated High

This tool deploys infrastructure by executing a docker-compose configuration on a VPS, which runs containers and external operations. The severity is high because it can replace existing projects (potentially destructive side effect) and deploy arbitrary code from URLs or GitHub repositories, giving broad execution capability on remote infrastructure.

From the tool's definition Deploy new project from docker-compose.yaml contents... existing project will be replaced

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_createNewProjectV1 Rate-limited

VPS_createNewProjectV1 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_createNewProjectV1": {
      "limits": [
        {
          "counter": "vps_createnewprojectv1_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_createNewProjectV1 call is checked against it from then on.

FAQ

Questions about VPS_createNewProjectV1

What does the VPS_createNewProjectV1 tool do? +

Deploy new project from docker-compose.yaml contents or download contents from URL. URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents. If project with the same name already exists, existing project will be replaced. 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_createNewProjectV1 accept? +

VPS_createNewProjectV1 accepts 4 parameters: content, environment, project_name, virtualMachineId. Required: content, project_name, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_createNewProjectV1? +

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

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

Can I rate-limit VPS_createNewProjectV1? +

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

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

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