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

WHAT IT DOES

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

Why StopJob needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StopJob Rate-limited

StopJob 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": {
    "StopJob": {
      "limits": [
        {
          "counter": "stopjob_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 StopJob

What does the StopJob tool do? +

Stop a currently running job. 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 StopJob? +

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

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

Can I rate-limit StopJob? +

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

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

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