VPS_getProjectListV1
Retrieves a list of all Docker Compose projects currently deployed on the virtual machine. This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitt...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getprojectlistv1.md
What VPS_getProjectListV1 does on Hostinger Api
AI agents call VPS_getProjectListV1 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_getProjectListV1 is rated Low
This tool retrieves and queries Docker project and container information from a VPS instance with no ability to modify, delete, or execute operations. It is a read-only operation that gathers existing data about deployed projects. The blast radius of misuse is limited to information disclosure about project configuration and status.
From the tool's definition Retrieves a list of all Docker Compose projects...returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports.
Attacks that exploit this kind of access
The rule that runs VPS_getProjectListV1 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_getProjectListV1, this is the rule to start with:
VPS_getProjectListV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_getProjectListV1 call is checked against it from then on.
Questions about VPS_getProjectListV1
Retrieves a list of all Docker Compose projects currently deployed on the virtual machine. This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitted in this endpoint. If you need to get detailed information about container with stats included, use the Get project containers endpoint. Use this to get an overview of all Docker projects on your VPS instance. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getProjectListV1 accepts 1 parameter: virtualMachineId. Required: 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_getProjectListV1: 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_getProjectListV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the VPS_getProjectListV1 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_getProjectListV1. 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_getProjectListV1 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.
This server
Across the catalogue