# start_server

Запускает выключенный VPS. Идемпотентен: на уже работающем сервере вернёт ошибку. Проверь статус через get_server перед вызовом.

Agent View of the PolicyLayer registry record for `start_server`. HTML page: https://policylayer.com/tools/timeweb-mcp/start-server

## Facts

- Tool: `start_server`
- Server: Timeweb (`timeweb-mcp`) — https://policylayer.com/tools/timeweb-mcp.md
- Install: `npx -y timeweb-mcp`
- Homepage: https://www.npmjs.com/package/timeweb-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `server_id` | number | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сервера для запуска |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "start_server",
    "arguments": {
      "server_id": 0
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Timeweb:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_server": {
      "limits": [
        {
          "counter": "start_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Timeweb (244)

- `delete_ai_agent` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-ai-agent.md
- `delete_api_key` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-api-key.md
- `delete_balancer` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-balancer.md
- `delete_balancer_rule` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-balancer-rule.md
- `delete_bucket` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-bucket.md
- `delete_bucket_subdomains` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-bucket-subdomains.md
- `delete_container_registry` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-container-registry.md
- `delete_database_admin` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-database-admin.md
- `delete_database_cluster` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-database-cluster.md
- `delete_dedicated_server` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-dedicated-server.md
- `delete_dns_record` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-dns-record.md
- `delete_domain` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-domain.md
- `delete_firewall_group` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-firewall-group.md
- `delete_firewall_rule` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-firewall-rule.md
- `delete_floating_ip` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-floating-ip.md
- `delete_image` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-image.md
- `delete_image_download` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-image-download.md
- `delete_k8s_cluster` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-k8s-cluster.md
- `delete_k8s_cluster_node` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-k8s-cluster-node.md
- `delete_k8s_node_group` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-k8s-node-group.md
- `delete_mailbox` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-mailbox.md
- `delete_network_drive` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-network-drive.md
- `delete_project` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-project.md
- `delete_server` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-server.md
- `delete_server_disk_backup` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-server-disk-backup.md
- `delete_server_ip` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-server-ip.md
- `delete_ssh_key` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-ssh-key.md
- `delete_subdomain` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-subdomain.md
- `delete_vpc` — Destructive — https://policylayer.com/tools/timeweb-mcp/delete-vpc.md
- `hard_reboot_server` — Destructive — https://policylayer.com/tools/timeweb-mcp/hard-reboot-server.md
- …and 214 more: https://policylayer.com/tools/timeweb-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=timeweb-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/timeweb-mcp