rename-collection · Mongodb3 MCP: Risk & Policy

WHAT IT DOES

What rename-collection does on Mongodb3

AI agents use rename-collection to create or update resources in Mongodb3 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mongodb3 environment.

WHY IT NEEDS A POLICY

Why rename-collection needs a policy

Renaming a collection is a structural modification that changes metadata in the database. While reversible (the collection can be renamed again), it can break applications that depend on the original name and affects data accessibility. This makes it a Write operation rather than Destructive (since the data itself persists and the operation is undoable).

From the tool's definition Tool name is 'rename-collection' and description states it will 'Rename a collection in a database'. This modifies the structure and identity of a collection, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename-collection Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename-collection": {
      "limits": [
        {
          "counter": "rename-collection_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 Mongodb3, so you can run agents against it safely.

FAQ

Questions about rename-collection

What does the rename-collection tool do? +

Rename a collection in a database. It is categorised as a Write tool in the Mongodb3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename-collection? +

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

What risk level is rename-collection? +

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

Can I rate-limit rename-collection? +

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

How do I block rename-collection completely? +

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

What MCP server provides rename-collection? +

rename-collection is provided by the Mongodb3 MCP server (mongodb3-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.