update_container_registry

Изменяет параметры реестра контейнеров: описание, тариф (preset_id) или кастомную конфигурацию (configurator_id + disk). Имя реестра изменить нельзя.

SERVERTimeweb SOURCEtimeweb-mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/timeweb-mcp/update-container-registry.md

WHAT IT DOES

What update_container_registry does on Timeweb

AI agents use update_container_registry to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.

Parameter	Type	Required	Description
`disk`	number	—	Для configurator-режима: размер диска в ГБ. ОБЯЗАТЕЛЬНО если передан configurator_id.
`preset_id`	number	—	Новый ID тарифа. Нельзя вместе с configurator_id.
`description`	string	—	Новое описание реестра
`registry_id`	number	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID реестра для обновления
`configurator_id`	number	—	ID конфигуратора для кастомной конфигурации. Нельзя вместе с preset_id.

Parameters from the server's own tool schema.

RISK

Why update_container_registry is rated Medium

An AI agent can call update_container_registry faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_container_registry, this is the rule to start with:

update_container_registry Rate-limited

update_container_registry stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_container_registry": {
      "limits": [
        {
          "counter": "update_container_registry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every update_container_registry call is checked against it from then on.

FAQ

Questions about update_container_registry

What does the update_container_registry tool do? +

Изменяет параметры реестра контейнеров: описание, тариф (preset_id) или кастомную конфигурацию (configurator_id + disk). Имя реестра изменить нельзя. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_container_registry accept? +

update_container_registry accepts 5 parameters: disk, preset_id, description, registry_id, configurator_id. Required: registry_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_container_registry? +

Register the Timeweb MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_container_registry? +

update_container_registry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_container_registry? +

Yes. Add a rate_limit block to the update_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.

How do I block update_container_registry completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_container_registry? +

update_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.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →