VPS_getProjectContainersV1
Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine. This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration. Use this to monitor the health and state of all servi...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getprojectcontainersv1.md
What VPS_getProjectContainersV1 does on Hostinger Api
AI agents call VPS_getProjectContainersV1 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 |
|---|---|---|---|
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_getProjectContainersV1 is rated Low
This tool only retrieves and queries container information for a Docker Compose project. It performs no modifications, deletions, or state changes. The blast radius if misused by an AI agent is minimal—at worst, an attacker gains visibility into container configurations and status, which is informational only.
From the tool's definition Endpoint description states 'Retrieves a list of all containers' and 'returns detailed information' with explicit mention of monitoring functionality.
Attacks that exploit this kind of access
The rule that runs VPS_getProjectContainersV1 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_getProjectContainersV1, this is the rule to start with:
VPS_getProjectContainersV1 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_getProjectContainersV1 call is checked against it from then on.
Questions about VPS_getProjectContainersV1
Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine. This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration. Use this to monitor the health and state of all services within your Docker Compose project. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getProjectContainersV1 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_getProjectContainersV1: 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_getProjectContainersV1 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_getProjectContainersV1 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_getProjectContainersV1. 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_getProjectContainersV1 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