delete_database_cluster
Удаляет кластер баз данных (DELETE /api/v1/databases/{db_cluster_id}). Для аккаунтов с 2FA в ответе вернётся hash — повторите запрос с ним и с code из аутентификатора.
This record as markdown: /tools/timeweb-mcp/delete-database-cluster.md
What delete_database_cluster does on Timeweb
AI agents call delete_database_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 (возвращается после первого запроса для аккаунтов с 2FA) |
db_cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера для удаления |
Parameters from the server's own tool schema.
Why delete_database_cluster is rated Critical
An AI agent that decides to call delete_database_cluster 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.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs delete_database_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_database_cluster, this is the rule to start with:
delete_database_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_database_cluster call is checked against it from then on.
Questions about delete_database_cluster
Удаляет кластер баз данных (DELETE /api/v1/databases/{db_cluster_id}). Для аккаунтов с 2FA в ответе вернётся 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_database_cluster accepts 3 parameters: code, hash, db_cluster_id. Required: db_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_database_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_database_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_database_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_database_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_database_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