List all Cosmos DB containers in a database
AI agents call cosmosdb_container_list to retrieve information from Azure MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval-only operation (list) that queries existing containers in a Cosmos DB database. It has no side effects, does not modify data, and does not execute commands or trigger external operations. The blast radius of misuse is minimal—an attacker gains visibility into container names and structure but cannot modify, delete, or access data without additional tools.
From the tool's definition Tool name 'cosmosdb_container_list' and description 'List all Cosmos DB containers in a database' indicate a query operation that retrieves information without modifying or executing operations.
Attacks that exploit this kind of access
List all Cosmos DB containers in a database. It is categorised as a Read tool in the Azure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure MCP Server MCP server in PolicyLayer and add a rule for cosmosdb_container_list: 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_list 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 cosmosdb_container_list 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_list. 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_list 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 →