VPS_getMetricsV1
Retrieve historical metrics for a specified virtual machine. It includes the following metrics: - CPU usage - Memory usage - Disk usage - Network usage - Uptime Use this endpoint to monitor VPS performance and resource utilization over time.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getmetricsv1.md
What VPS_getMetricsV1 does on Hostinger Api
AI agents call VPS_getMetricsV1 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 |
|---|---|---|---|
date_to | string | Yes | date_to parameter |
date_from | string | Yes | date_from parameter |
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_getMetricsV1 is rated Low
This tool purely queries and retrieves historical performance data about a VPS without making any changes, executing code, or triggering external operations. It is a straightforward read operation used for monitoring and observation only.
From the tool's definition Tool name includes 'get' and description states 'Retrieve historical metrics' with no mention of modifications, deletions, or side effects. It retrieves CPU usage, memory usage, disk usage, network usage, and uptime data for monitoring purposes.
Attacks that exploit this kind of access
The rule that runs VPS_getMetricsV1 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_getMetricsV1, this is the rule to start with:
VPS_getMetricsV1 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_getMetricsV1 call is checked against it from then on.
Questions about VPS_getMetricsV1
Retrieve historical metrics for a specified virtual machine. It includes the following metrics: - CPU usage - Memory usage - Disk usage - Network usage - Uptime Use this endpoint to monitor VPS performance and resource utilization over time. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getMetricsV1 accepts 3 parameters: date_to, date_from, virtualMachineId. Required: date_to, date_from, 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_getMetricsV1: 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_getMetricsV1 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_getMetricsV1 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_getMetricsV1. 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_getMetricsV1 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