update_ssh_key
Изменяет параметры SSH-ключа по ID. Можно обновить имя, тело ключа и/или флаг is_default. Передавай только те поля, которые нужно изменить.
This record as markdown: /tools/timeweb-mcp/update-ssh-key.md
What update_ssh_key does on Timeweb
AI agents use update_ssh_key to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | Новое тело публичного SSH-ключа (опц.) |
name | string | — | Новое имя SSH-ключа (опц.) |
is_default | boolean | — | Сделать ключ дефолтным при создании новых серверов (true/false, опц.) |
ssh_key_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID SSH-ключа |
Parameters from the server's own tool schema.
Why update_ssh_key is rated Medium
This tool modifies SSH key configuration reversibly. While it doesn't delete data, updating SSH keys—especially the key body itself—can have significant security implications if misused by an agent (e.g., replacing valid keys with attacker-controlled ones, disabling default keys).
From the tool's definition Tool name 'update_ssh_key' and description 'Изменяет параметры SSH-ключа' (Changes SSH key parameters) indicate modification of an existing SSH key resource. The description explicitly lists updateable fields: name, key body (тело ключа), and is_default flag.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_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 update_ssh_key, this is the rule to start with:
update_ssh_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_ssh_key call is checked against it from then on.
Questions about update_ssh_key
Изменяет параметры SSH-ключа по ID. Можно обновить имя, тело ключа и/или флаг is_default. Передавай только те поля, которые нужно изменить. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_ssh_key accepts 4 parameters: body, name, is_default, 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 update_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.
update_ssh_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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