Disable a job (prevents scheduled execution).
AI agents use DisableJob to create or update resources in Veeam VBR v13 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Veeam VBR v13 MCP Server environment.
DisableJob modifies the enabled/disabled state of a backup job, which is a reversible change to system configuration. This falls under Write (creates or modifies data reversibly) rather than Execute or Destructive because: (1) no code execution or external operations triggered, (2) the change is reversible via EnableJob, (3) it affects backup job scheduling behavior.
From the tool's definition Tool name 'DisableJob' and description 'Disable a job (prevents scheduled execution)' indicates modification of job state/configuration.
Attacks that exploit this kind of access
Disable a job (prevents scheduled execution). It is categorised as a Write tool in the Veeam VBR v13 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for DisableJob: 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.
DisableJob is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the DisableJob 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 DisableJob. 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.
DisableJob 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 →