mcp_update_document
A write tool on the Mongo- MCP server.
This record as markdown: /tools/441126098-mongo-mcp/mcp-update-document.md
What mcp_update_document does on Mongo-MCP
AI agents use mcp_update_document to create or update resources in Mongo-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mongo-MCP environment.
Why mcp_update_document is rated Medium
The tool modifies existing data reversibly (updating rather than deleting), making it Write rather than Destructive. However, severity is high because uncontrolled updates to production MongoDB data could corrupt critical information, affect many records, or violate business logic. Confidence is 0.95 despite empty description because the name is unambiguous and the server context is clear.
From the tool's definition Tool name 'mcp_update_document' indicates modification of existing data in MongoDB. Sibling tools include destructive operations (mcp_delete_document, mcp_drop_collection) and read operations (mcp_count_documents, mcp_distinct_values), placing this tool in…
Attacks that exploit this kind of access
The rule that runs mcp_update_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mongo-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_update_document, this is the rule to start with:
mcp_update_document 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mongo-MCP, apply this rule, and every mcp_update_document call is checked against it from then on.
Questions about mcp_update_document
mcp_update_document is a write tool on the Mongo MCP server. It is categorised as a Write tool in the Mongo-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mongo MCP server in PolicyLayer and add a rule for mcp_update_document: 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 Mongo-MCP. Nothing to install.
mcp_update_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mcp_update_document 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 mcp_update_document. 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.
mcp_update_document is provided by the Mongo MCP server (441126098/mongo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mongo, and thousands of servers like it.
This server
Across the catalogue