start_server
Запускает выключенный VPS. Идемпотентен: на уже работающем сервере вернёт ошибку. Проверь статус через get_server перед вызовом.
This record as markdown: /tools/timeweb-mcp/start-server.md
What start_server does on Timeweb
AI agents invoke start_server to trigger actions in Timeweb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
server_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера для запуска |
Parameters from the server's own tool schema.
Why start_server is rated High
start_server triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs start_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 start_server, this is the rule to start with:
start_server stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 start_server call is checked against it from then on.
Questions about start_server
Запускает выключенный VPS. Идемпотентен: на уже работающем сервере вернёт ошибку. Проверь статус через get_server перед вызовом. It is categorised as a Execute tool in the Timeweb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
start_server accepts 1 parameter: server_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 start_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.
start_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_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 start_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.
start_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.
Across the catalogue