Remove a cloud credentials record.
AI agents call DeleteCloudCreds 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.
Deletion of cloud credentials is irreversible and cannot be undone. Misuse could render cloud integrations non-functional, disrupt backup operations, and cause loss of access to critical cloud infrastructure. This is a destructive action that qualifies as high severity given the operational impact on a backup/replication system.
From the tool's definition Tool name 'DeleteCloudCreds' and description 'Remove a cloud credentials record' indicate permanent deletion of credentials data.
Attacks that exploit this kind of access
Remove a cloud credentials record. 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 DeleteCloudCreds: 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.
DeleteCloudCreds 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 DeleteCloudCreds 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 DeleteCloudCreds. 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.
DeleteCloudCreds 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 →