Delete a job from the Veeam Backup server.
AI agents call DeleteJob to permanently remove resources in Veeam VBR v13 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a backup job is a destructive action that cannot be undone. It removes the job configuration from the Veeam server, potentially halting backups and losing job history/settings. This is not reversible through the same tool and represents a high-impact change to backup infrastructure that an AI agent could misuse by deleting critical backup jobs.
From the tool's definition Tool name is 'DeleteJob' and description states 'Delete a job from the Veeam Backup server.' The word 'Delete' combined with permanent removal of a backup job configuration represents irreversible data loss.
Attacks that exploit this kind of access
Delete a job from the Veeam Backup server. It is categorised as a Destructive tool in the Veeam VBR v13 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for DeleteJob: 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.
DeleteJob is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the DeleteJob 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 DeleteJob. 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.
DeleteJob 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →