RescanManagedServer
Rescan a specific managed server.
This record as markdown: /tools/kid-boy-veeam-mcp-13/rescanmanagedserver.md
What RescanManagedServer does on Veeam VBR v13 MCP Server
AI agents invoke RescanManagedServer 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 RescanManagedServer is rated High
Rescanning a managed server initiates an external operation that queries and updates the state of the server's inventory within Veeam VBR. This is not a passive read (it actively triggers a rescan job), nor does it irreversibly delete data. It falls under Execute as it triggers an external operation whose effects (inventory refresh, potential state changes) depend on the target server.
From the tool's definition 'Rescan a specific managed server' — triggers an active scanning/discovery operation against external infrastructure
Attacks that exploit this kind of access
The rule that runs RescanManagedServer 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 RescanManagedServer, this is the rule to start with:
RescanManagedServer 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every RescanManagedServer call is checked against it from then on.
Questions about RescanManagedServer
Rescan a specific managed server. 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.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for RescanManagedServer: 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.
RescanManagedServer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the RescanManagedServer 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 RescanManagedServer. 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.
RescanManagedServer 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.
More on Veeam VBR v13 MCP Server, and thousands of servers like it.
Across the catalogue