list_container_registry_repositories
Возвращает список репозиториев (образов) внутри конкретного реестра контейнеров: имя репозитория, тег, digest, размер. Используй чтобы посмотреть, какие образы уже загружены в реестр.
This record as markdown: /tools/timeweb-mcp/list-container-registry-repositories.md
What list_container_registry_repositories does on Timeweb
AI agents call list_container_registry_repositories 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
registry_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID реестра (получить через list_container_registries) |
Parameters from the server's own tool schema.
Why list_container_registry_repositories is rated Low
This tool queries and retrieves metadata about container images in a registry (name, tag, digest, size). It performs no write, delete, execute, or financial operations. It is a pure read operation that returns existing data with no side effects. Severity is low as unauthorized listing of repository metadata poses minimal direct risk compared to other categories.
From the tool's definition Tool description states it 'Возвращает список репозиториев' (returns a list of repositories) and 'посмотреть, какие образы уже загружены' (see which images are already loaded).
Attacks that exploit this kind of access
The rule that runs list_container_registry_repositories 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_registry_repositories, this is the rule to start with:
list_container_registry_repositories 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_registry_repositories call is checked against it from then on.
Questions about list_container_registry_repositories
Возвращает список репозиториев (образов) внутри конкретного реестра контейнеров: имя репозитория, тег, digest, размер. Используй чтобы посмотреть, какие образы уже загружены в реестр. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
list_container_registry_repositories 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 list_container_registry_repositories: 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_registry_repositories 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_registry_repositories 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_registry_repositories. 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_registry_repositories 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