list_container_registries
Возвращает список всех реестров контейнеров (Container Registry) аккаунта: ID, имя, описание, тариф, использование диска, дата создания. Используй перед операциями над реестром, чтобы получить его ID.
This record as markdown: /tools/timeweb-mcp/list-container-registries.md
What list_container_registries does on Timeweb
AI agents call list_container_registries to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_container_registries is rated Low
This is a pure read operation that queries and retrieves container registry metadata. It has no side effects and is used to gather information before other operations. The sibling tools on the server (add_balancer_ips, add_bucket_to_project, etc.) suggest this is an infrastructure management API, but this particular tool is strictly informational.
From the tool's definition Tool name is 'list_container_registries' and description states it 'Возвращает список всех реестров контейнеров' (returns a list of all container registries) with retrieval of metadata (ID, name, description, plan, disk usage, creation date).
Attacks that exploit this kind of access
The rule that runs list_container_registries 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 list_container_registries, this is the rule to start with:
list_container_registries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every list_container_registries call is checked against it from then on.
Questions about list_container_registries
Возвращает список всех реестров контейнеров (Container Registry) аккаунта: ID, имя, описание, тариф, использование диска, дата создания. Используй перед операциями над реестром, чтобы получить его ID. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
Register the Timeweb MCP server in PolicyLayer and add a rule for list_container_registries: 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.
list_container_registries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_container_registries 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 list_container_registries. 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.
list_container_registries 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.
This server
Across the catalogue