delete_subdomain
Удаляет поддомен по его FQDN из указанного основного домена.
This record as markdown: /tools/timeweb-mcp/delete-subdomain.md
What delete_subdomain does on Timeweb
AI agents call delete_subdomain 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 |
|---|---|---|---|
fqdn | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя основного домена |
subdomain_fqdn | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя удаляемого поддомена |
Parameters from the server's own tool schema.
Why delete_subdomain is rated Critical
This tool irreversibly removes a subdomain from a domain. Deletion of DNS records and associated routing cannot be undone without manual intervention. The high severity reflects that inadvertent deletion could disrupt services, break existing URLs, and impact production infrastructure.
From the tool's definition Tool name is 'delete_subdomain' and the Russian description translates to 'Deletes a subdomain by its FQDN from the specified primary domain.' The verb 'Удаляет' (deletes) indicates permanent removal.
Attacks that exploit this kind of access
The rule that runs delete_subdomain 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_subdomain, this is the rule to start with:
delete_subdomain 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_subdomain call is checked against it from then on.
Questions about delete_subdomain
Удаляет поддомен по его FQDN из указанного основного домена. 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_subdomain accepts 2 parameters: fqdn, subdomain_fqdn. Required: fqdn, subdomain_fqdn. 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_subdomain: 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_subdomain 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_subdomain 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_subdomain. 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_subdomain 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