StartJob
Start/run a specific job immediately. Returns a session ID to track progress.
This record as markdown: /tools/kid-boy-veeam-mcp-13/startjob.md
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 StartJob is rated High
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
The rule that runs StartJob 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 StartJob, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every StartJob call is checked against it from then on.
Questions about StartJob
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.
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.
StartJob is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Veeam VBR v13 MCP Server, and thousands of servers like it.
Across the catalogue