get_bucket_transfer_status
Возвращает статус переноса хранилища от стороннего S3-провайдера в Timeweb Cloud: started/suspended/failed, количество и размер объектов, перенесено, попытки, ошибки. Используй после transfer_bucket.
This record as markdown: /tools/timeweb-mcp/get-bucket-transfer-status.md
What get_bucket_transfer_status does on Timeweb
AI agents call get_bucket_transfer_status to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bucket_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID S3-хранилища |
Parameters from the server's own tool schema.
Why get_bucket_transfer_status is rated Low
This tool only retrieves and queries the status of an existing bucket transfer operation. It returns metadata (status state, object counts, sizes, error information) without creating, modifying, deleting, or executing any operations. The verb 'returns' and the read-only nature of status checks classify this as a Read operation with low severity.
From the tool's definition Tool description states it 'returns' (Возвращает) transfer status and metrics - a purely informational query with no side effects.
Attacks that exploit this kind of access
The rule that runs get_bucket_transfer_status 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 get_bucket_transfer_status, this is the rule to start with:
get_bucket_transfer_status is read-only, so it stays allowed. 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 get_bucket_transfer_status call is checked against it from then on.
Questions about get_bucket_transfer_status
Возвращает статус переноса хранилища от стороннего S3-провайдера в Timeweb Cloud: started/suspended/failed, количество и размер объектов, перенесено, попытки, ошибки. Используй после transfer_bucket. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
get_bucket_transfer_status accepts 1 parameter: bucket_id. Required: bucket_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 get_bucket_transfer_status: 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.
get_bucket_transfer_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_bucket_transfer_status 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 get_bucket_transfer_status. 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.
get_bucket_transfer_status 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.
This server
Across the catalogue