Query items in a Cosmos DB container using SQL
AI agents invoke cosmosdb_item_query to trigger actions in Azure MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes SQL queries against a Cosmos DB container. While typical usage may be read-only, arbitrary SQL execution can include operations with side effects or be used to extract large volumes of sensitive data. The ability to run arbitrary SQL elevates this beyond a simple Read tool. Severity is high due to potential for data exfiltration or unintended query execution at scale across a cloud database.
From the tool's definition 'Query items in a Cosmos DB container using SQL' — executes arbitrary SQL queries against Cosmos DB
Attacks that exploit this kind of access
Query items in a Cosmos DB container using SQL. It is categorised as a Execute tool in the Azure MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Azure MCP Server MCP server in PolicyLayer and add a rule for cosmosdb_item_query: 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_item_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cosmosdb_item_query 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_item_query. 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_item_query 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 →