update_dedicated_server
Изменяет параметры выделенного сервера: имя и/или комментарий. Оба поля опциональны, но хотя бы одно должно быть передано.
This record as markdown: /tools/timeweb-mcp/update-dedicated-server.md
What update_dedicated_server does on Timeweb
AI agents use update_dedicated_server 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 | — | Новое имя сервера (до 255 символов, уникальное) |
comment | string | — | Новый комментарий к серверу (до 255 символов) |
dedicated_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID выделенного сервера |
Parameters from the server's own tool schema.
Why update_dedicated_server is rated Medium
The tool creates or modifies data (server name and comments) in a reversible manner without deleting or executing arbitrary code. It falls clearly into the Write category. Severity is medium because changing server metadata could cause operational confusion or impact monitoring/identification, but the changes are non-destructive and reversible.
From the tool's definition Tool name 'update_dedicated_server' and description states 'Изменяет параметры выделенного сервера' (Changes parameters of a dedicated server) with optional fields for name and/or comment. This modifies server metadata reversibly.
Attacks that exploit this kind of access
The rule that runs update_dedicated_server 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_dedicated_server, this is the rule to start with:
update_dedicated_server 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_dedicated_server call is checked against it from then on.
Questions about update_dedicated_server
Изменяет параметры выделенного сервера: имя и/или комментарий. Оба поля опциональны, но хотя бы одно должно быть передано. 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_dedicated_server accepts 3 parameters: name, comment, dedicated_id. Required: dedicated_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_dedicated_server: 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_dedicated_server 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_dedicated_server 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_dedicated_server. 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_dedicated_server 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