SetAgentConsumption · Veeam VBR v13 MCP Server MCP

WHAT IT DOES

What SetAgentConsumption does on Veeam VBR v13 MCP Server

AI agents use SetAgentConsumption 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.

WHY IT NEEDS A POLICY

Why SetAgentConsumption needs a policy

This tool modifies licensing and consumption policies for agents, affecting their operational permissions and resource allocation. While reversible (can be toggled on/off), such changes have significant downstream effects on infrastructure capacity, compliance posture, and agent functionality. It is not destructive (no data deletion), not financial (no payment/obligation), and not execute (no command execution).

From the tool's definition 'Enable or disable instance consumption for unlicensed agents' — modifies agent licensing state and resource consumption settings, which are reversible configuration changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

SetAgentConsumption Rate-limited

SetAgentConsumption 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": {
    "SetAgentConsumption": {
      "limits": [
        {
          "counter": "setagentconsumption_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 SetAgentConsumption

What does the SetAgentConsumption tool do? +

Enable or disable instance consumption for unlicensed agents. 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 SetAgentConsumption? +

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

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

Can I rate-limit SetAgentConsumption? +

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

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

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