Browse the contents of a Veeam Data Cloud Vault.
AI agents call BrowseCloudVaultEntity to retrieve information from Veeam VBR v13 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about cloud vault contents. While it is a read operation with no direct side effects, the moderate severity reflects that unauthorized browsing of backup vault contents could expose sensitive data (backup metadata, schedules, stored system configurations). The blast radius is bounded to information disclosure rather than data modification or destruction.
From the tool's definition Tool name 'Browse' and description 'Browse the contents of a Veeam Data Cloud Vault' indicate data retrieval/querying operations without modification. The verb 'browse' is a read-only action.
Attacks that exploit this kind of access
Browse the contents of a Veeam Data Cloud Vault. It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for BrowseCloudVaultEntity: 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.
BrowseCloudVaultEntity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the BrowseCloudVaultEntity 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 BrowseCloudVaultEntity. 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.
BrowseCloudVaultEntity 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →