Update a single document in a collection
AI agents use updateOne 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.
updateOne modifies data but does not irreversibly delete or destroy it. The operation is reversible (a subsequent update can undo changes), placing it in the Write category rather than Destructive. Severity is high because a misconfigured AI agent could update critical documents in unintended ways, affecting data integrity across a collection, though the impact is mitigable through rollback operations.
From the tool's definition Tool name 'updateOne' and description 'Update a single document in a collection' indicate modification of existing data.
Attacks that exploit this kind of access
Update a single document in a collection. 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.
Register the MongoDB MCP Server MCP server in PolicyLayer and add a rule for updateOne: 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.
updateOne 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 updateOne 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 updateOne. 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.
updateOne is provided by the MongoDB MCP Server MCP server (ryaker/mongodb-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 →