mcp_rename_collection
A write tool on the Mongo- MCP server.
This record as markdown: /tools/441126098-mongo-mcp/mcp-rename-collection.md
What mcp_rename_collection does on Mongo-MCP
AI agents use mcp_rename_collection 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_rename_collection is rated Medium
Renaming a collection is a write operation—it modifies collection metadata reversibly without deleting data or executing arbitrary code. However, it ranks as 'high' severity because an agent misusing this could rename critical collections, causing application failures, confusion, or service disruption if the collection names are hardcoded or expected by dependent systems.
From the tool's definition Tool name 'mcp_rename_collection' indicates modification of collection metadata. Sibling tools include 'mcp_drop_collection' (destructive) and 'mcp_create_collection' (write). Renaming is a reversible structural modification to a collection.
Attacks that exploit this kind of access
The rule that runs mcp_rename_collection 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_rename_collection, this is the rule to start with:
mcp_rename_collection 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_rename_collection call is checked against it from then on.
Questions about mcp_rename_collection
mcp_rename_collection 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_rename_collection: 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_rename_collection 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_rename_collection 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_rename_collection. 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_rename_collection 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