reboot_server
Мягко перезагружает сервер через ACPI reboot. ОС корректно завершает процессы перед рестартом. Используй для применения обновлений ядра или сброса подвисшего состояния.
This record as markdown: /tools/timeweb-mcp/reboot-server.md
What reboot_server does on Timeweb
AI agents invoke reboot_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 reboot_server is rated High
This tool triggers a server reboot operation — an external action that disrupts running services and processes. While it's a 'soft' reboot (ACPI) and not permanently destructive, it executes an operation with significant blast radius: all running services on the server are interrupted. This classifies as Execute (triggering external operations) with high severity due to potential service disruption.
From the tool's definition Мягко перезагружает сервер через ACPI reboot. ОС корректно завершает процессы перед рестартом.
Attacks that exploit this kind of access
The rule that runs reboot_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 reboot_server, this is the rule to start with:
reboot_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 reboot_server call is checked against it from then on.
Questions about reboot_server
Мягко перезагружает сервер через ACPI reboot. ОС корректно завершает процессы перед рестартом. Используй для применения обновлений ядра или сброса подвисшего состояния. 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.
reboot_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 reboot_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.
reboot_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 reboot_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 reboot_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.
reboot_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