delete_container_registry
Удаляет реестр контейнеров безвозвратно. ⚠️ Все образы в реестре будут потеряны. Перед удалением убедись, что реестр не используется.
This record as markdown: /tools/timeweb-mcp/delete-container-registry.md
What delete_container_registry does on Timeweb
AI agents call delete_container_registry 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 |
|---|---|---|---|
registry_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID реестра для удаления |
Parameters from the server's own tool schema.
Why delete_container_registry is rated Critical
This tool permanently and irreversibly deletes a container registry and all its contents. The effects cannot be undone, making it clearly destructive. The warning symbol and explicit statement about permanent loss confirm this is a high-severity destructive operation that could cause significant operational disruption if invoked unintentionally.
From the tool's definition Tool name contains 'delete_container_registry'; description states 'Удаляет реестр контейнеров безвозвратно' (deletes container registry irreversibly) and '⚠️ Все образы в реестре будут потеряны' (all images in the registry will be lost).
Attacks that exploit this kind of access
The rule that runs delete_container_registry 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_container_registry, this is the rule to start with:
delete_container_registry 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_container_registry call is checked against it from then on.
Questions about delete_container_registry
Удаляет реестр контейнеров безвозвратно. ⚠️ Все образы в реестре будут потеряны. Перед удалением убедись, что реестр не используется. 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_container_registry accepts 1 parameter: registry_id. Required: registry_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_container_registry: 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_container_registry 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_container_registry 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_container_registry. 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_container_registry 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