transfer_project_resource
Переносит сервер/БД/балансировщик/хранилище/кластер/dedicated из одного проекта в другой. resource_type обязателен.
This record as markdown: /tools/timeweb-mcp/transfer-project-resource.md
What transfer_project_resource does on Timeweb
AI agents use transfer_project_resource to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
resource_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID переносимого ресурса |
resource_type | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип ресурса: server | balancer | database | kubernetes | storage | dedicated |
to_project_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID проекта-приёмника |
from_project_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID проекта-источника |
Parameters from the server's own tool schema.
Why transfer_project_resource is rated Medium
This tool moves/transfers resources between projects, which is a reversible organizational change (Write). It does not delete or destroy data, execute code, or involve financial transactions. Misuse could cause resource misassignment but is generally recoverable.
From the tool's definition Переносит сервер/БД/балансировщик/хранилище/кластер/dedicated из одного проекта в другой
Attacks that exploit this kind of access
The rule that runs transfer_project_resource 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_project_resource, this is the rule to start with:
transfer_project_resource stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 transfer_project_resource call is checked against it from then on.
Questions about transfer_project_resource
Переносит сервер/БД/балансировщик/хранилище/кластер/dedicated из одного проекта в другой. resource_type обязателен. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
transfer_project_resource accepts 4 parameters: resource_id, resource_type, to_project_id, from_project_id. Required: resource_id, resource_type, to_project_id, from_project_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 transfer_project_resource: 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_project_resource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the transfer_project_resource 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_project_resource. 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_project_resource 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