transfer_bucket
Запускает перенос S3-хранилища от стороннего провайдера (указывается endpoint, access_key, secret_key, имя bucket) в Timeweb Cloud под именем new_bucket_name. Мониторь прогресс через get_bucket_transfer_status.
This record as markdown: /tools/timeweb-mcp/transfer-bucket.md
What transfer_bucket does on Timeweb
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.
| 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.
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 signalsAccepts URL/endpoint input (endpoint)
Attacks that exploit this kind of access
The rule that runs transfer_bucket 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 transfer_bucket, this is the rule to start with:
Any call to transfer_bucket is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every transfer_bucket call is checked against it from then on.
Questions about transfer_bucket
Запускает перенос S3-хранилища от стороннего провайдера (указывается endpoint, access_key, secret_key, имя bucket) в Timeweb Cloud под именем new_bucket_name. Мониторь прогресс через get_bucket_transfer_status. It is categorised as a Financial tool in the Timeweb MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
transfer_bucket accepts 7 parameters: endpoint, location, access_key, secret_key, bucket_name, new_bucket_name, is_force_path_style. Required: endpoint, location, access_key, secret_key, bucket_name, new_bucket_name, is_force_path_style. 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 transfer_bucket: 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.
transfer_bucket is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer_bucket 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 transfer_bucket. 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.
transfer_bucket 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