VPS_getPublicKeysV1
Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getpublickeysv1.md
What VPS_getPublicKeysV1 does on Hostinger Api
AI agents call VPS_getPublicKeysV1 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 |
Parameters from the server's own tool schema.
Why VPS_getPublicKeysV1 is rated Low
This tool retrieves SSH public keys for informational purposes only. While SSH keys are security-sensitive, the read operation itself poses no direct risk of data loss, execution, or financial impact. The blast radius of accidental misuse is minimal since retrieval of public keys (which are, by nature, public) does not compromise security or enable attacks.
From the tool's definition Tool name contains 'get' and description states 'Retrieve public keys' and 'view available SSH keys' — these are read-only operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs VPS_getPublicKeysV1 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_getPublicKeysV1, this is the rule to start with:
VPS_getPublicKeysV1 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_getPublicKeysV1 call is checked against it from then on.
Questions about VPS_getPublicKeysV1
Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
VPS_getPublicKeysV1 accepts 1 parameter: page. 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_getPublicKeysV1: 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_getPublicKeysV1 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_getPublicKeysV1 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_getPublicKeysV1. 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_getPublicKeysV1 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