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

WHAT IT DOES

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

Why StopSession needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StopSession Rate-limited

StopSession 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": {
    "StopSession": {
      "limits": [
        {
          "counter": "stopsession_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 StopSession

What does the StopSession tool do? +

Stop a running session. 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 StopSession? +

Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for StopSession: 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 StopSession? +

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

Can I rate-limit StopSession? +

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

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

StopSession 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.