clone_server
Создаёт полную копию сервера в отдельный VPS с такой же конфигурацией и данными. Использовать для миграций, blue-green deploy или тестирования рискованных операций на копии.
This record as markdown: /tools/timeweb-mcp/clone-server.md
What clone_server does on Timeweb
AI agents invoke clone_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 clone_server is rated High
This tool creates a full clone of a server into a new VPS instance. It triggers an external infrastructure operation (provisioning a new VPS) that has significant side effects and resource implications. It is not purely destructive (original is preserved), not financial in a direct sense, but it executes a complex infrastructure action.
From the tool's definition Создаёт полную копию сервера в отдельный VPS с такой же конфигурацией и данными
Attacks that exploit this kind of access
The rule that runs clone_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 clone_server, this is the rule to start with:
clone_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 clone_server call is checked against it from then on.
Questions about clone_server
Создаёт полную копию сервера в отдельный VPS с такой же конфигурацией и данными. Использовать для миграций, blue-green deploy или тестирования рискованных операций на копии. 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.
clone_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 clone_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.
clone_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 clone_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 clone_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.
clone_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