This record as markdown: /tools/hostinger-mcp/vps-get-snapshot.md
What vps_get_snapshot does on Hostinger
AI agents call vps_get_snapshot to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vps_get_snapshot is rated Low
This tool retrieves information about VPS snapshots without performing any side effects, modifications, or destructive actions. It falls squarely into the Read category as a data retrieval operation. The low severity reflects the minimal risk of misuse—retrieving snapshot metadata poses no direct threat to system integrity or financial impact.
From the tool's definition Tool name 'vps_get_snapshot' and description 'Get snapshot details' indicate a query/retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs vps_get_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vps_get_snapshot, this is the rule to start with:
vps_get_snapshot 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, apply this rule, and every vps_get_snapshot call is checked against it from then on.
Questions about vps_get_snapshot
Get snapshot details. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for vps_get_snapshot: 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. Nothing to install.
vps_get_snapshot 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_get_snapshot 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_get_snapshot. 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_get_snapshot is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue