Remove latency settings for a specific datastore.
AI agents call DeleteDatastoreLatencySettings to permanently remove resources in Veeam VBR v13 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting datastore latency settings removes configuration that cannot be trivially restored and may impact backup performance tuning. While not data destruction at the scope of entire backups, it is an irreversible configuration deletion that requires manual reconfiguration to undo. This qualifies as Destructive rather than Write (which is reversible modification).
From the tool's definition Tool name contains 'Delete' and description states 'Remove latency settings' — both indicate irreversible deletion of configuration data.
Attacks that exploit this kind of access
Remove latency settings for a specific datastore. It is categorised as a Destructive tool in the Veeam VBR v13 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for DeleteDatastoreLatencySettings: 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.
DeleteDatastoreLatencySettings is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the DeleteDatastoreLatencySettings 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 DeleteDatastoreLatencySettings. 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.
DeleteDatastoreLatencySettings 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 →