StartFlrMount

What StartFlrMount does on Veeam VBR v13 MCP Server

AI agents invoke StartFlrMount to trigger actions in Veeam VBR v13 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.

Why StartFlrMount is rated High

This tool executes a backup mount operation, which is an external system action whose effects depend on user-supplied parameters. While not destructive (the mount is reversible), it goes beyond simple data retrieval and actively triggers infrastructure operations. The high severity reflects that an AI agent could inadvertently mount sensitive backup data or disrupt normal operations if parameters are misused.

From the tool's definition StartFlrMount initiates a file restore session by mounting a backup, which is an operational action that triggers external effects (mounting backup storage) that depend on which backup and restore point are specified as arguments.

The rule that runs StartFlrMount safely

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

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

Questions about StartFlrMount