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

WHAT IT DOES

What StartJob does on Veeam VBR v13 MCP Server

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

This tool executes a pre-defined job in the Veeam backup system. While the job itself is pre-configured (mitigating some risk), the act of triggering its execution qualifies as Execute because: (1) it runs an operation with real-world side effects on the backup infrastructure, (2) the consequences depend on job configuration which may be unknown to the AI agent, (3) a misconfigured or maliciously-configured job…

From the tool's definition Tool description states 'Start/run a specific job immediately' - this triggers execution of a backup/recovery job in the Veeam infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StartJob Rate-limited

StartJob 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": {
    "StartJob": {
      "limits": [
        {
          "counter": "startjob_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 StartJob

What does the StartJob tool do? +

Start/run a specific job immediately. Returns a session ID to track progress. 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 StartJob? +

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

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

Can I rate-limit StartJob? +

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

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

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