get_ssh_key
Возвращает детальную информацию об SSH-ключе по его ID: имя, тело ключа, дата создания, is_default и список серверов, где он используется.
This record as markdown: /tools/timeweb-mcp/get-ssh-key.md
What get_ssh_key does on Timeweb
AI agents call get_ssh_key to retrieve information from Timeweb 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 |
|---|---|---|---|
ssh_key_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID SSH-ключа |
Parameters from the server's own tool schema.
Why get_ssh_key is rated Low
This is a Read operation as it retrieves and queries data with no side effects. However, the severity is elevated to 'high' rather than 'low' because the returned data includes the SSH key body itself, which is sensitive authentication credential that could be misused by a malicious actor to gain unauthorized access to systems.
From the tool's definition Tool name 'get_ssh_key' and description 'Returns detailed information about SSH key by its ID: name, key body, creation date, is_default and list of servers where it is used.' — retrieves sensitive authentication material (SSH key body) and metadata.
Attacks that exploit this kind of access
The rule that runs get_ssh_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ssh_key, this is the rule to start with:
get_ssh_key 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 Timeweb, apply this rule, and every get_ssh_key call is checked against it from then on.
Questions about get_ssh_key
Возвращает детальную информацию об SSH-ключе по его ID: имя, тело ключа, дата создания, is_default и список серверов, где он используется. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
get_ssh_key accepts 1 parameter: ssh_key_id. Required: ssh_key_id. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for 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 Timeweb. Nothing to install.
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 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 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.
get_ssh_key is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue