delete_server_disk_backup
Удаляет бэкап диска сервера. Действие необратимо. Перед удалением стоит убедиться через list_server_disk_backups что это не последний актуальный бэкап.
This record as markdown: /tools/timeweb-mcp/delete-server-disk-backup.md
What delete_server_disk_backup does on Timeweb
AI agents call delete_server_disk_backup 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 |
|---|---|---|---|
disk_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID диска |
backup_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID бэкапа для удаления |
server_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера |
Parameters from the server's own tool schema.
Why delete_server_disk_backup is rated Critical
An AI agent that decides to call delete_server_disk_backup doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Timeweb is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_server_disk_backup 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_disk_backup, this is the rule to start with:
delete_server_disk_backup 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_disk_backup call is checked against it from then on.
Questions about delete_server_disk_backup
Удаляет бэкап диска сервера. Действие необратимо. Перед удалением стоит убедиться через list_server_disk_backups что это не последний актуальный бэкап. 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_disk_backup accepts 3 parameters: disk_id, backup_id, server_id. Required: disk_id, backup_id, 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_disk_backup: 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_disk_backup 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_disk_backup 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_disk_backup. 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_disk_backup 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