delete_database_admin
Удаляет пользователя кластера базы данных (DELETE /api/v1/databases/{db_cluster_id}/admins/{admin_id}). Действие необратимо.
This record as markdown: /tools/timeweb-mcp/delete-database-admin.md
What delete_database_admin does on Timeweb
AI agents call delete_database_admin 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 |
|---|---|---|---|
admin_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID пользователя для удаления |
db_cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера базы данных |
Parameters from the server's own tool schema.
Why delete_database_admin is rated Critical
This tool permanently removes database cluster admin users with no undo capability. While not a complete data loss event, deletion of administrative access is irreversible and could disrupt database operations or remove critical system accounts. This qualifies as Destructive rather than Execute because the action cannot be reversed and the primary effect is removal of a resource.
From the tool's definition Tool description explicitly states "Удаляет пользователя" (deletes a user) and "Действие необратимо" (action is irreversible). The endpoint is a DELETE operation on database admin resources.
Attacks that exploit this kind of access
The rule that runs delete_database_admin 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_admin, this is the rule to start with:
delete_database_admin 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_admin call is checked against it from then on.
Questions about delete_database_admin
Удаляет пользователя кластера базы данных (DELETE /api/v1/databases/{db_cluster_id}/admins/{admin_id}). Действие необратимо. 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_admin accepts 2 parameters: admin_id, db_cluster_id. Required: admin_id, 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_admin: 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_admin 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_admin 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_admin. 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_admin 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