mount_network_drive
Подключает сетевой диск к сервису (серверу). Сервис и диск должны быть в одной зоне доступности. Доступные для подключения сервисы можно получить через list_network_drive_available_resources.
This record as markdown: /tools/timeweb-mcp/mount-network-drive.md
What mount_network_drive does on Timeweb
AI agents use mount_network_drive 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 | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID ресурса (например, ID сервера) — узнать через list_network_drive_available_resources |
resource_type | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - Тип ресурса, к которому подключаем диск (сейчас поддерживается только server) |
network_drive_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID сетевого диска (UUID) |
Parameters from the server's own tool schema.
Why mount_network_drive is rated Medium
This tool mounts/attaches a network drive to a service (server). This is a reversible write operation — it creates a connection/attachment between resources. It does not delete or irreversibly destroy data, nor does it execute code or move money. Misuse could cause service disruption or unauthorized data access, hence medium severity.
From the tool's definition Подключает сетевой диск к сервису (серверу) — 'подключает' means 'connects/mounts', indicating a reversible attachment operation
Attacks that exploit this kind of access
The rule that runs mount_network_drive 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 mount_network_drive, this is the rule to start with:
mount_network_drive 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 mount_network_drive call is checked against it from then on.
Questions about mount_network_drive
Подключает сетевой диск к сервису (серверу). Сервис и диск должны быть в одной зоне доступности. Доступные для подключения сервисы можно получить через list_network_drive_available_resources. 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.
mount_network_drive accepts 3 parameters: resource_id, resource_type, network_drive_id. Required: resource_id, resource_type, network_drive_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 mount_network_drive: 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.
mount_network_drive 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 mount_network_drive 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 mount_network_drive. 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.
mount_network_drive 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