StopJob

What StopJob does on Veeam VBR v13 MCP Server

AI agents invoke StopJob 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 StopJob is rated High

StopJob performs an active intervention on running infrastructure rather than passively reading data (Read) or creating reversible changes (Write). While not destructive in the sense of deleting data, it interrupts critical backup/replication operations which could have significant blast radius—a stopped backup job in production may leave systems unprotected, miss recovery objectives, or leave data in inconsistent…

From the tool's definition Tool name 'StopJob' and description 'Stop a currently running job' indicate the tool triggers an external operation (stopping a Veeam backup/replication job) whose effects depend on which job is targeted.

The rule that runs StopJob 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 StopJob, this is the rule to start with:

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

Questions about StopJob