delete_server
Удаляет сервер. Для аккаунтов с 2FA первый вызов возвращает hash — повторный вызов с hash и code завершит удаление. Удалённый сервер может быть перемещён в карантин.
This record as markdown: /tools/timeweb-mcp/delete-server.md
What delete_server does on Timeweb
AI agents call delete_server 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) |
hash | string | — | Хеш (для аккаунтов с 2FA, выдаётся после первого DELETE-запроса) |
server_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера для удаления |
Parameters from the server's own tool schema.
Why delete_server is rated Critical
Deleting a server is an irreversible action that destroys or removes infrastructure and its associated resources. This is a core destructive operation with severe consequences (data loss, service disruption, potential unrecoverability). The critical severity reflects the high blast radius—an AI agent executing this without proper intent could destroy production infrastructure.
From the tool's definition Tool name is 'delete_server'; description states 'Удаляет сервер' (deletes server) and 'Удалённый сервер может быть перемещён в карантин' (deleted server may be moved to quarantine), indicating permanent or near-permanent removal of infrastructure.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs delete_server 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_server, this is the rule to start with:
delete_server 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_server call is checked against it from then on.
Questions about delete_server
Удаляет сервер. Для аккаунтов с 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_server accepts 3 parameters: code, hash, server_id. Required: server_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_server: 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_server 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_server 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_server. 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_server 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