Delete a Cosmos DB container
AI agents call cosmosdb_container_delete to permanently remove resources in Azure MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a Cosmos DB container is a destructive operation that cannot be undone and results in permanent data loss. This represents the most severe category applicable. The high severity reflects the blast radius of an AI agent accidentally or maliciously invoking this against a production container.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a Cosmos DB container' — this irreversibly removes an entire container and all its data.
Attacks that exploit this kind of access
Delete a Cosmos DB container. It is categorised as a Destructive tool in the Azure MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Azure MCP Server MCP server in PolicyLayer and add a rule for cosmosdb_container_delete: 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 Azure MCP Server. Nothing to install.
cosmosdb_container_delete 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 cosmosdb_container_delete 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 cosmosdb_container_delete. 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.
cosmosdb_container_delete is provided by the Azure MCP Server MCP server (mashriram/azure_mcp_server). 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 →