put_item · Azure Cosmos DB MCP Server MCP: Risk & Policy

WHAT IT DOES

What put_item does on Azure Cosmos DB MCP Server

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

WHY IT NEEDS A POLICY

Why put_item needs a policy

This tool creates or modifies data in a reversible manner (items can be updated or deleted again). It does not permanently destroy data (Destructive), does not move money (Financial), and does not execute arbitrary code (Execute). While 'replace' could suggest overwriting, the reversible nature and the presence of sibling tools like update_item indicate this is standard Write-category database operation.

From the tool's definition Tool description states 'Inserts or replaces an item in a Azure Cosmos DB container'. The verb 'inserts or replaces' indicates data modification without destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

put_item Rate-limited

put_item 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": {
    "put_item": {
      "limits": [
        {
          "counter": "put_item_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 Cosmos DB MCP Server, so you can run agents against it safely.

FAQ

Questions about put_item

What does the put_item tool do? +

Inserts or replaces an item in a Azure Cosmos DB container. It is categorised as a Write tool in the Azure Cosmos DB 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 put_item? +

Register the Azure Cosmos DB MCP Server MCP server in PolicyLayer and add a rule for put_item: 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 Cosmos DB MCP Server. Nothing to install.

What risk level is put_item? +

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

Can I rate-limit put_item? +

Yes. Add a rate_limit block to the put_item 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 put_item completely? +

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

put_item is provided by the Azure Cosmos DB MCP Server MCP server (robinong79/mcp-cosmos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.