project_access_list_update · MongoDB Atlas MCP Server MCP

WHAT IT DOES

What project_access_list_update does on MongoDB Atlas MCP Server

AI agents use project_access_list_update to create or update resources in MongoDB Atlas MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MongoDB Atlas MCP Server environment.

WHY IT NEEDS A POLICY

Why project_access_list_update needs a policy

This tool modifies the IP access list for a MongoDB Atlas project, controlling which IPs can access the project. While it uses POST semantics (Write), misconfiguration could expose the database to unauthorized access or lock out legitimate users, making the blast radius high. It is reversible (entries can be updated again), so it falls under Write rather than Destructive.

From the tool's definition "Update IP access list entries for the project (POST semantics)"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_access_list_update Rate-limited

project_access_list_update 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": {
    "project_access_list_update": {
      "limits": [
        {
          "counter": "project_access_list_update_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 MongoDB Atlas MCP Server, so you can run agents against it safely.

FAQ

Questions about project_access_list_update

What does the project_access_list_update tool do? +

Update IP access list entries for the project (POST semantics). It is categorised as a Write tool in the MongoDB Atlas MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on project_access_list_update? +

Register the MongoDB Atlas MCP Server MCP server in PolicyLayer and add a rule for project_access_list_update: 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 Atlas MCP Server. Nothing to install.

What risk level is project_access_list_update? +

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

Can I rate-limit project_access_list_update? +

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

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

project_access_list_update is provided by the MongoDB Atlas MCP Server MCP server (montumodi/mongodb-atlas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.