create_container_registry

SERVERTimeweb SOURCEtimeweb-mcp

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What create_container_registry does on Timeweb

AI agents use create_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.
`name`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - Имя реестра. Уникальное, 3-48 символов, только [a-z0-9-], без пробелов
`preset_id`	number	—	Режим 1: ID готового тарифа (получить через list_container_registry_presets). Нельзя вместе с configurator_id.
`project_id`	number	—	ID проекта, в который добавить реестр (опц.)
`description`	string	—	Описание реестра (опц.)
`configurator_id`	number	—	Режим 2: ID конфигуратора для кастомной конфигурации. Нельзя вместе с preset_id.

Parameters from the server's own tool schema.

RISK

Why create_container_registry is rated Medium

An AI agent can call create_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 create_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 create_container_registry, this is the rule to start with:

create_container_registry Rate-limited

create_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": {
    "create_container_registry": {
      "limits": [
        {
          "counter": "create_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 create_container_registry call is checked against it from then on.

FAQ

Questions about create_container_registry

What does the create_container_registry tool do? +

Создаёт новый реестр контейнеров (Container Registry). Укажи либо preset_id (готовый тариф), либо configurator_id + disk (кастомная конфигурация). Имя должно быть уникальным, 3-48 символов, только [a-z0-9-]. 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 create_container_registry accept? +

create_container_registry accepts 6 parameters: disk, name, preset_id, project_id, description, configurator_id. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_container_registry? +

Register the Timeweb MCP server in PolicyLayer and add a rule for create_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 create_container_registry? +

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

Can I rate-limit create_container_registry? +

Yes. Add a rate_limit block to the create_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 create_container_registry completely? +

Set action: deny in the PolicyLayer policy for create_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 create_container_registry? +

create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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