get_container_registry
Возвращает детальную информацию о конкретном реестре контейнеров по ID: имя, описание, тариф, использование диска, дата создания и обновления.
This record as markdown: /tools/timeweb-mcp/get-container-registry.md
What get_container_registry does on Timeweb
AI agents call get_container_registry 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 get_container_registry is rated Low
Even though get_container_registry only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_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 get_container_registry, this is the rule to start with:
get_container_registry 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 get_container_registry call is checked against it from then on.
Questions about get_container_registry
Возвращает детальную информацию о конкретном реестре контейнеров по ID: имя, описание, тариф, использование диска, дата создания и обновления. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_container_registry 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 get_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 get_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.
get_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.
This server
Across the catalogue