VPS_deleteProjectV1
Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images. This operation is irreversible and will delete all project data. Use this when you want to permanently remove a project and f...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-deleteprojectv1.md
What VPS_deleteProjectV1 does on Hostinger Api
AI agents call VPS_deleteProjectV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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.
Why VPS_deleteProjectV1 is rated Critical
This tool performs an irreversible deletion of virtual machine infrastructure and data. The description explicitly states the operation is irreversible and will delete all project data, including containers, networks, volumes, and images. This meets the Destructive category definition of actions that cannot be undone.
From the tool's definition 'Completely removes a Docker Compose project', 'stopping all containers and cleaning up associated resources including networks, volumes, and images', 'This operation is irreversible', 'delete all project data'
Attacks that exploit this kind of access
The rule that runs VPS_deleteProjectV1 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_deleteProjectV1, this is the rule to start with:
VPS_deleteProjectV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_deleteProjectV1 call is checked against it from then on.
Questions about VPS_deleteProjectV1
Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images. This operation is irreversible and will delete all project data. Use this when you want to permanently remove a project and free up system resources. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
VPS_deleteProjectV1 accepts 2 parameters: projectName, virtualMachineId. Required: projectName, 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_deleteProjectV1: 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_deleteProjectV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the VPS_deleteProjectV1 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_deleteProjectV1. 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_deleteProjectV1 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.
Across the catalogue