Remove a Microsoft Entra ID tenant.
AI agents call DeleteEntraIDTenants 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 an Entra ID tenant is an irreversible action that destroys identity infrastructure, potentially affecting all users, applications, and access controls tied to that tenant. This is a classic destructive operation with severe blast radius. The action cannot be reversed without recreating the entire tenant from backup.
From the tool's definition Tool name 'DeleteEntraIDTenants' and description 'Remove a Microsoft Entra ID tenant' explicitly perform deletion of directory/identity infrastructure that cannot be undone.
Attacks that exploit this kind of access
Remove a Microsoft Entra ID tenant. 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 DeleteEntraIDTenants: 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.
DeleteEntraIDTenants 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 DeleteEntraIDTenants 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 DeleteEntraIDTenants. 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.
DeleteEntraIDTenants 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 →