update_k8s_cluster_version
Обновляет версию Kubernetes в кластере. Версию можно не передавать — тогда будет выбрана следующая доступная.
This record as markdown: /tools/timeweb-mcp/update-k8s-cluster-version.md
What update_k8s_cluster_version does on Timeweb
AI agents invoke update_k8s_cluster_version to trigger actions in Timeweb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера |
k8s_version | string | — | Новая версия Kubernetes (например, v1.33.4+k0s.0). Получить список через list_k8s_versions. |
Parameters from the server's own tool schema.
Why update_k8s_cluster_version is rated High
Upgrading a Kubernetes cluster version is an operational action that executes a significant infrastructure change. It is not purely a write (it triggers active processes on live infrastructure), not destructive (data is not deleted), and not financial. It has high blast radius because a failed or unintended upgrade can cause cluster downtime or compatibility issues.
From the tool's definition Обновляет версию Kubernetes в кластере — triggers a Kubernetes cluster version upgrade operation
Attacks that exploit this kind of access
The rule that runs update_k8s_cluster_version 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_k8s_cluster_version, this is the rule to start with:
update_k8s_cluster_version stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_k8s_cluster_version call is checked against it from then on.
Questions about update_k8s_cluster_version
Обновляет версию Kubernetes в кластере. Версию можно не передавать — тогда будет выбрана следующая доступная. It is categorised as a Execute tool in the Timeweb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
update_k8s_cluster_version accepts 2 parameters: cluster_id, k8s_version. Required: cluster_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_k8s_cluster_version: 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_k8s_cluster_version is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the update_k8s_cluster_version 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_k8s_cluster_version. 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_k8s_cluster_version 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.
Across the catalogue