mcp_replace_document
A write tool on the Mongo- MCP server.
This record as markdown: /tools/441126098-mongo-mcp/mcp-replace-document.md
What mcp_replace_document does on Mongo-MCP
AI agents use mcp_replace_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_replace_document is rated Medium
Document replacement is a write operation that modifies data but remains reversible—the old document can be recovered from backups or application logs, and the action itself is not permanent deletion. However, severity is high due to the potential for significant data modification and the risk of an AI agent replacing critical documents with incorrect values.
From the tool's definition Tool name 'mcp_replace_document' indicates it modifies/overwrites existing documents. Description is empty, but sibling tools include destructive operations (mcp_delete_document, mcp_drop_collection) and the server provides 'complete suite of CRUD operations'…
Attacks that exploit this kind of access
The rule that runs mcp_replace_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_replace_document, this is the rule to start with:
mcp_replace_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_replace_document call is checked against it from then on.
Questions about mcp_replace_document
mcp_replace_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_replace_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_replace_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_replace_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_replace_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_replace_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