mount_disk

A execute tool on the 1Panel MCP server.

SERVER1Panel MCP Server SOURCEeaveluo/1panel-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eaveluo-1panel-mcp/mount-disk.md

WHAT IT DOES

What mount_disk does on 1Panel MCP Server

AI agents invoke mount_disk to trigger actions in 1Panel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why mount_disk is rated High

Mounting a disk is an Execute-category action as it triggers an external system operation (attaching a storage device to the filesystem). It is not purely destructive (it doesn't delete data), but it can have significant system-level consequences if misused, such as mounting malicious or unintended storage devices, overriding existing mount points, or exposing sensitive data.

From the tool's definition 'Mount disk' - mounting a disk is a system-level operation that attaches storage devices to the filesystem, triggering external OS-level operations with significant system impact

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mount_disk safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mount_disk, this is the rule to start with:

mount_disk Rate-limited

mount_disk stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mount_disk": {
      "limits": [
        {
          "counter": "mount_disk_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every mount_disk call is checked against it from then on.

FAQ

Questions about mount_disk

What does the mount_disk tool do? +

mount_disk is a execute tool on the 1Panel MCP Server MCP server. It is categorised as a Execute tool in the 1Panel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mount_disk? +

Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for mount_disk: 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 1Panel MCP Server. Nothing to install.

What risk level is mount_disk? +

mount_disk is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mount_disk? +

Yes. Add a rate_limit block to the mount_disk 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.

How do I block mount_disk completely? +

Set action: deny in the PolicyLayer policy for mount_disk. 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.

What MCP server provides mount_disk? +

mount_disk is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1Panel MCP Server, and thousands of servers like it.

This server

All 286 1Panel MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →