VPS_getProjectLogsV1
Retrieves aggregated log entries from all services within a Docker Compose project. This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services. Use this for debugging, monitoring applic...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getprojectlogsv1.md
What VPS_getProjectLogsV1 does on Hostinger Api
AI agents call VPS_getProjectLogsV1 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_getProjectLogsV1 is rated Low
This tool performs a read-only operation that queries and retrieves existing log data from Docker Compose services. It has no capability to modify, delete, execute commands, or trigger side effects. The purpose is explicitly diagnostic (debugging, monitoring, troubleshooting).
From the tool's definition Tool retrieves log entries with no modification capability - 'Retrieves aggregated log entries', 'returns recent log output', 'for debugging, monitoring'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs VPS_getProjectLogsV1 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_getProjectLogsV1, this is the rule to start with:
VPS_getProjectLogsV1 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_getProjectLogsV1 call is checked against it from then on.
Questions about VPS_getProjectLogsV1
Retrieves aggregated log entries from all services within a Docker Compose project. This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services. Use this for debugging, monitoring application behavior, and troubleshooting issues across your entire project stack. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getProjectLogsV1 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_getProjectLogsV1: 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_getProjectLogsV1 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_getProjectLogsV1 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_getProjectLogsV1. 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_getProjectLogsV1 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