delete_k8s_cluster
Удаляет Kubernetes-кластер. Действие необратимо. Для аккаунтов с 2FA: первый вызов возвращает hash, затем повторный вызов с hash и code подтверждает удаление.
This record as markdown: /tools/timeweb-mcp/delete-k8s-cluster.md
What delete_k8s_cluster does on Timeweb
AI agents call delete_k8s_cluster to permanently remove resources in Timeweb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | Код подтверждения из приложения 2FA |
hash | string | — | Хэш, полученный при первом запросе удаления (для аккаунтов с 2FA) |
cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера для удаления |
Parameters from the server's own tool schema.
Why delete_k8s_cluster is rated Critical
This tool irreversibly deletes a Kubernetes cluster, which represents complete loss of that infrastructure resource. The Russian description explicitly confirms the action cannot be undone ('необратимо'). Even with 2FA confirmation flow, the underlying operation is permanent deletion.
From the tool's definition Tool name 'delete_k8s_cluster' and description states 'Удаляет Kubernetes-кластер' (deletes Kubernetes cluster) with explicit note 'Действие необратимо' (action is irreversible). The tool performs permanent deletion of infrastructure.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs delete_k8s_cluster 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 delete_k8s_cluster, this is the rule to start with:
delete_k8s_cluster is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every delete_k8s_cluster call is checked against it from then on.
Questions about delete_k8s_cluster
Удаляет Kubernetes-кластер. Действие необратимо. Для аккаунтов с 2FA: первый вызов возвращает hash, затем повторный вызов с hash и code подтверждает удаление. It is categorised as a Destructive tool in the Timeweb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_k8s_cluster accepts 3 parameters: code, hash, cluster_id. 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 delete_k8s_cluster: 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.
delete_k8s_cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_k8s_cluster 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 delete_k8s_cluster. 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.
delete_k8s_cluster 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