cosmosdb_container_create · Azure MCP Server MCP

WHAT IT DOES

What cosmosdb_container_create does on Azure MCP Server

AI agents use cosmosdb_container_create to create or update resources in Azure MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure MCP Server environment.

WHY IT NEEDS A POLICY

Why cosmosdb_container_create needs a policy

Creating a Cosmos DB container is a reversible write operation that provisions a new data storage resource. While it modifies cloud infrastructure state and incurs potential costs, it does not delete data or execute arbitrary code.

From the tool's definition Tool name includes 'create' and description states 'Create a new Cosmos DB container'. This is a write operation that modifies infrastructure state by creating a new database resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cosmosdb_container_create Rate-limited

cosmosdb_container_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cosmosdb_container_create": {
      "limits": [
        {
          "counter": "cosmosdb_container_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure MCP Server, so you can run agents against it safely.

FAQ

Questions about cosmosdb_container_create

What does the cosmosdb_container_create tool do? +

Create a new Cosmos DB container. It is categorised as a Write tool in the Azure MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cosmosdb_container_create? +

Register the Azure MCP Server MCP server in PolicyLayer and add a rule for cosmosdb_container_create: 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.

What risk level is cosmosdb_container_create? +

cosmosdb_container_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cosmosdb_container_create? +

Yes. Add a rate_limit block to the cosmosdb_container_create 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.

How do I block cosmosdb_container_create completely? +

Set action: deny in the PolicyLayer policy for cosmosdb_container_create. 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.

What MCP server provides cosmosdb_container_create? +

cosmosdb_container_create 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.