VPS_getAttachedPublicKeysV1

Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances.

SERVERHostinger Api SOURCEhostinger-api-mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-getattachedpublickeysv1.md

What VPS_getAttachedPublicKeysV1 does on Hostinger Api

AI agents call VPS_getAttachedPublicKeysV1 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.

ParameterTypeRequiredDescription
page integer Page number
virtualMachineId integer Yes Virtual Machine ID

Parameters from the server's own tool schema.

Why VPS_getAttachedPublicKeysV1 is rated Low

This tool retrieves information about SSH public keys attached to a VPS instance. It performs a data lookup without modifying, deleting, or executing anything. The information returned (public keys) is generally non-sensitive from a confidentiality standpoint in typical SSH configurations, and the operation has no blast radius beyond information disclosure. Classified as Read with low severity.

From the tool's definition Tool name contains 'get' and description states 'Retrieve public keys' and 'view SSH keys configured' — these are read-only query operations with no side effects.

Questions about VPS_getAttachedPublicKeysV1

What does the VPS_getAttachedPublicKeysV1 tool do? +

Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does VPS_getAttachedPublicKeysV1 accept? +

VPS_getAttachedPublicKeysV1 accepts 2 parameters: page, virtualMachineId. Required: virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_getAttachedPublicKeysV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_getAttachedPublicKeysV1: 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.

What risk level is VPS_getAttachedPublicKeysV1? +

VPS_getAttachedPublicKeysV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit VPS_getAttachedPublicKeysV1? +

Yes. Add a rate_limit block to the VPS_getAttachedPublicKeysV1 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.

How do I block VPS_getAttachedPublicKeysV1 completely? +

Set action: deny in the PolicyLayer policy for VPS_getAttachedPublicKeysV1. 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.

What MCP server provides VPS_getAttachedPublicKeysV1? +

VPS_getAttachedPublicKeysV1 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.