DisableJob

Disable a job (prevents scheduled execution).

SERVERVeeam VBR v13 MCP Server SOURCEkid-boy/veeam-mcp-13

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kid-boy-veeam-mcp-13/disablejob.md

WHAT IT DOES

What DisableJob does on Veeam VBR v13 MCP Server

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.

RISK

Why DisableJob is rated Medium

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

RECOMMENDED RULE

The rule that runs DisableJob 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 DisableJob, this is the rule to start with:

DisableJob Rate-limited

DisableJob stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "DisableJob": {
      "limits": [
        {
          "counter": "disablejob_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every DisableJob call is checked against it from then on.

FAQ

Questions about DisableJob

What does the DisableJob tool do? +

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.

How do I enforce a policy on DisableJob? +

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.

What risk level is DisableJob? +

DisableJob is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit DisableJob? +

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.

How do I block DisableJob completely? +

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.

What MCP server provides DisableJob? +

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.

KEEP EXPLORING

More on Veeam VBR v13 MCP Server, and thousands of servers like it.

This server

All 328 Veeam VBR v13 MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →