resize_server
Меняет тариф (preset_id) или кастомную конфигурацию (configurator_id + cpu/ram/disk/gpu). Применяется к существующему серверу — потребуется downtime. Для получения списка presets используй get_allowed_presets.
This record as markdown: /tools/timeweb-mcp/resize-server.md
What resize_server does on Timeweb
AI agents use resize_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 |
|---|---|---|---|
cpu | number | — | Для configurator-режима: количество ядер CPU |
gpu | number | — | Для configurator-режима: количество GPU |
ram | number | — | Для configurator-режима: RAM в МБ |
disk | number | — | Для configurator-режима: размер диска в МБ |
preset_id | number | — | Режим 1: ID готового тарифа. Нельзя использовать вместе с configurator_id. |
server_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера |
configurator_id | number | — | Режим 2: ID конфигуратора (для кастомной конфигурации). Нельзя использовать вместе с preset_id. |
Parameters from the server's own tool schema.
Why resize_server is rated Medium
An AI agent can call resize_server faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs resize_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 resize_server, this is the rule to start with:
resize_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 resize_server call is checked against it from then on.
Questions about resize_server
Меняет тариф (preset_id) или кастомную конфигурацию (configurator_id + cpu/ram/disk/gpu). Применяется к существующему серверу — потребуется downtime. Для получения списка presets используй get_allowed_presets. 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.
resize_server accepts 7 parameters: cpu, gpu, ram, disk, preset_id, server_id, configurator_id. Required: server_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 resize_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.
resize_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 resize_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 resize_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.
resize_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