StopAutomationSession · Veeam VBR v13 MCP Server MCP

WHAT IT DOES

What StopAutomationSession does on Veeam VBR v13 MCP Server

AI agents invoke StopAutomationSession 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 StopAutomationSession needs a policy

Stopping an automation session is an Execute action because it triggers an external operation (termination of a running process) whose effects depend on what that session is performing. While not destructive (the session can be restarted), it interrupts active backup, recovery, or replication workflows in a Veeam infrastructure, potentially impacting data protection operations.

From the tool's definition Tool name 'StopAutomationSession' and description 'Stop a running automation session' indicate termination of an active process or operation. The action interrupts an ongoing system operation, which is a form of execution control with external effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StopAutomationSession Rate-limited

StopAutomationSession 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": {
    "StopAutomationSession": {
      "limits": [
        {
          "counter": "stopautomationsession_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 StopAutomationSession

What does the StopAutomationSession tool do? +

Stop a running automation 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 StopAutomationSession? +

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

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

Can I rate-limit StopAutomationSession? +

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

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

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