StartFlrMount · Veeam VBR v13 MCP Server MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why StartFlrMount needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StartFlrMount Rate-limited

StartFlrMount 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": {
    "StartFlrMount": {
      "limits": [
        {
          "counter": "startflrmount_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Veeam VBR v13 MCP Server, so you can run agents against it safely.

FAQ

Questions about StartFlrMount

What does the StartFlrMount tool do? +

Start a file restore session (mount backup for file-level restore). It is categorised as a Execute tool in the Veeam VBR v13 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 StartFlrMount? +

Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for StartFlrMount: 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 Veeam VBR v13 MCP Server. Nothing to install.

What risk level is StartFlrMount? +

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

Can I rate-limit StartFlrMount? +

Yes. Add a rate_limit block to the StartFlrMount 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 StartFlrMount completely? +

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

StartFlrMount is provided by the Veeam VBR v13 MCP Server MCP server (kid-boy/veeam-mcp-13). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.