# transfer_bucket

Запускает перенос S3-хранилища от стороннего провайдера (указывается endpoint, access_key, secret_key, имя bucket) в Timeweb Cloud под именем new_bucket_name. Мониторь прогресс через get_bucket_transfer_status.

Agent View of the PolicyLayer registry record for `transfer_bucket`. HTML page: https://policylayer.com/tools/timeweb-mcp/transfer-bucket

## Facts

- Tool: `transfer_bucket`
- 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: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 7 (7 required)
- Recommended policy verdict: Approval-gated

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `endpoint` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - URL источника (например 'https://s3.test.ru') |
| `location` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - регион источника, например 'ru-1' |
| `access_key` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - access_key от стороннего S3-хранилища |
| `secret_key` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - secret_key от стороннего S3-хранилища |
| `bucket_name` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - имя хранилища источника |
| `new_bucket_name` | string | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - имя хранилища-получателя в Timeweb Cloud |
| `is_force_path_style` | boolean | yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - принудительно использовать path-style URL для S3-объектов |

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": "transfer_bucket",
    "arguments": {
      "endpoint": "<endpoint>",
      "location": "<location>",
      "access_key": "<access_key>",
      "secret_key": "<secret_key>",
      "bucket_name": "<bucket_name>",
      "new_bucket_name": "<new_bucket_name>",
      "is_force_path_style": false
    }
  }
}
```

## Why transfer_bucket is rated Critical

transfer_bucket moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Risk signals: Accepts URL/endpoint input (endpoint)

## Use case

AI agents use transfer_bucket to commit financial operations through Timeweb, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_bucket": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

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