InstallAgentOnDiscoveredEntities

WHAT IT DOES

What InstallAgentOnDiscoveredEntities does on Veeam VBR v13 MCP Server

AI agents invoke InstallAgentOnDiscoveredEntities 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 InstallAgentOnDiscoveredEntities needs a policy

Installing software on remote systems is an external operation that modifies system state across potentially many machines. It is not simply writing data; it executes an installation process on discovered entities, which could affect a large number of systems (high blast radius). It doesn't delete data (not Destructive) nor involve finances, making Execute the most appropriate category.

From the tool's definition 'Install Veeam Agent on discovered entities' — triggers an installation operation across discovered infrastructure entities

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

InstallAgentOnDiscoveredEntities Rate-limited

InstallAgentOnDiscoveredEntities 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": {
    "InstallAgentOnDiscoveredEntities": {
      "limits": [
        {
          "counter": "installagentondiscoveredentities_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 InstallAgentOnDiscoveredEntities

What does the InstallAgentOnDiscoveredEntities tool do? +

Install Veeam Agent on discovered entities. 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 InstallAgentOnDiscoveredEntities? +

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

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

Can I rate-limit InstallAgentOnDiscoveredEntities? +

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

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

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