update_image
Обновляет имя и/или описание образа. Другие атрибуты (ОС, локация, disk_id) изменить нельзя.
This record as markdown: /tools/timeweb-mcp/update-image.md
What update_image does on Timeweb
AI agents use update_image 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 |
|---|---|---|---|
name | string | — | НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - новое имя образа |
image_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID образа |
description | string | — | НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - новое описание образа |
Parameters from the server's own tool schema.
Why update_image is rated Medium
This tool modifies image metadata (name and description) reversibly without deleting or destroying data. It falls under Write category as it creates or modifies data reversibly. Severity is medium because image metadata changes could affect infrastructure organization and visibility, but the operation is fully reversible and limited in scope to non-critical attributes.
From the tool's definition Tool name: update_image; Description states it 'updates name and/or description of an image' (Обновляет имя и/или описание образа), which are reversible modifications.
Attacks that exploit this kind of access
The rule that runs update_image 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_image, this is the rule to start with:
update_image 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every update_image call is checked against it from then on.
Questions about update_image
Обновляет имя и/или описание образа. Другие атрибуты (ОС, локация, disk_id) изменить нельзя. 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.
update_image accepts 3 parameters: name, image_id, description. Required: image_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 update_image: 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.
update_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_image 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 update_image. 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.
update_image 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