RescanRepositories · Veeam VBR v13 MCP Server MCP

WHAT IT DOES

What RescanRepositories does on Veeam VBR v13 MCP Server

AI agents invoke RescanRepositories 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 IT NEEDS A POLICY

Why RescanRepositories needs a policy

Rescanning repositories initiates an external operation against all configured backup repositories. It is not a simple read (it actively triggers a rescan process), nor does it delete or modify data. It falls under Execute as it triggers an infrastructure-wide operation whose effects (updated state, capacity refresh, potential side effects on ongoing jobs) depend on the current environment.

From the tool's definition 'Rescan all repositories to refresh their state and capacity' — triggers an active scanning operation across all repositories

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

RescanRepositories Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "RescanRepositories": {
      "limits": [
        {
          "counter": "rescanrepositories_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 RescanRepositories

What does the RescanRepositories tool do? +

Rescan all repositories to refresh their state and capacity. 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.

How do I enforce a policy on RescanRepositories? +

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

RescanRepositories is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit RescanRepositories? +

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

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

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