VPS_getActionsV1
Retrieve actions performed on a specified virtual machine. Actions are operations or events that have been executed on the virtual machine, such as starting, stopping, or modifying the machine. This endpoint allows you to view the history of these actions, providing details about each action, suc...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getactionsv1.md
What VPS_getActionsV1 does on Hostinger Api
AI agents call VPS_getActionsV1 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 |
|---|---|---|---|
page | integer | — | Page number |
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_getActionsV1 is rated Low
VPS_getActionsV1 queries and retrieves historical data about VM operations. It has no side effects, creates no resources, executes no commands, and modifies no state. This is a straightforward Read operation with minimal risk if misused — an attacker could only gain visibility into VM action history, not perform any operations or access sensitive data beyond audit logs.
From the tool's definition Tool description explicitly states 'Retrieve actions' and 'allows you to view the history' — pure information retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs VPS_getActionsV1 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_getActionsV1, this is the rule to start with:
VPS_getActionsV1 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_getActionsV1 call is checked against it from then on.
Questions about VPS_getActionsV1
Retrieve actions performed on a specified virtual machine. Actions are operations or events that have been executed on the virtual machine, such as starting, stopping, or modifying the machine. This endpoint allows you to view the history of these actions, providing details about each action, such as the action name, timestamp, and status. Use this endpoint to view VPS operation history and troubleshoot issues. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getActionsV1 accepts 2 parameters: page, 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_getActionsV1: 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_getActionsV1 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_getActionsV1 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_getActionsV1. 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_getActionsV1 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