shutdown_server
Мягко выключает сервер через ACPI shutdown (аналог нажатия кнопки питания). ОС корректно завершает процессы. Для принудительного выключения используй hard-shutdown через /action API (не покрыто этим tool-ом).
This record as markdown: /tools/timeweb-mcp/shutdown-server.md
What shutdown_server does on Timeweb
AI agents invoke shutdown_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 shutdown_server is rated High
This tool triggers an external operation (ACPI shutdown) on a server, causing it to power off. While it is a 'soft' shutdown that allows the OS to gracefully terminate processes, it is still an action that disrupts running services and has significant operational impact. It doesn't permanently destroy data but executes a real-world action with potentially high blast radius if misused on a production server.
From the tool's definition Мягко выключает сервер через ACPI shutdown (аналог нажатия кнопки питания). ОС корректно завершает процессы.
Attacks that exploit this kind of access
The rule that runs shutdown_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 shutdown_server, this is the rule to start with:
shutdown_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 shutdown_server call is checked against it from then on.
Questions about shutdown_server
Мягко выключает сервер через ACPI shutdown (аналог нажатия кнопки питания). ОС корректно завершает процессы. Для принудительного выключения используй hard-shutdown через /action API (не покрыто этим tool-ом). 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.
shutdown_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 shutdown_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.
shutdown_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 shutdown_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 shutdown_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.
shutdown_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