Get details of a specific SSH key by ID.
AI agents call hetzner_get_ssh_key to retrieve information from Hetzner MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about an existing SSH key without modifying, executing against, or deleting any resources. It is a straightforward data query operation, fitting the Read category. Severity is low because SSH key metadata retrieval poses minimal risk—no secrets are exposed (the private key itself is not returned), and the action is non-destructive and non-executable.
From the tool's definition Tool name 'hetzner_get_ssh_key' and description 'Get details of a specific SSH key by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a specific SSH key by ID. It is categorised as a Read tool in the Hetzner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_get_ssh_key: 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 Hetzner MCP Server. Nothing to install.
hetzner_get_ssh_key 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 hetzner_get_ssh_key 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 hetzner_get_ssh_key. 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.
hetzner_get_ssh_key is provided by the Hetzner MCP Server MCP server (jurislm/hetzner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →