StopSession

What StopSession does on Veeam VBR v13 MCP Server

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

Stopping a session is an operational action that terminates a running process or connection within Veeam Backup & Replication infrastructure. This is an Execute-class tool because it triggers an external operation with side effects that cannot be fully anticipated without knowing the session context (e.g., interrupting a backup job, recovery operation, or data transfer).

From the tool's definition The tool name is 'StopSession' and the description states it 'Stop[s] a running session.' This directly triggers an external operation (session termination) whose effect depends on which session is specified as an argument.

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

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

Questions about StopSession