update_document_by_id · MongoDB MCP Server MCP

WHAT IT DOES

What update_document_by_id does on MongoDB MCP Server

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

WHY IT NEEDS A POLICY

Why update_document_by_id needs a policy

This tool modifies data reversibly by updating a single document. It is not destructive (no deletion), not financial, and not execute (no arbitrary code execution). The 'high' severity reflects that document updates in production databases can have significant business impact if misused by an AI agent, but it remains 'Write' rather than 'Destructive' because updates are generally reversible through subsequent…

From the tool's definition Tool name 'update_document_by_id' and description 'Update a single document by its ObjectId' explicitly indicate modification of existing data. MongoDB CRUD operations context confirms this is a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_document_by_id Rate-limited

update_document_by_id 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": {
    "update_document_by_id": {
      "limits": [
        {
          "counter": "update_document_by_id_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 MongoDB MCP Server, so you can run agents against it safely.

FAQ

Questions about update_document_by_id

What does the update_document_by_id tool do? +

Update a single document by its ObjectId. It is categorised as a Write tool in the MongoDB 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 update_document_by_id? +

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

What risk level is update_document_by_id? +

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

Can I rate-limit update_document_by_id? +

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

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

update_document_by_id is provided by the MongoDB MCP Server MCP server (ruslankf777/mcp_mongo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.