// SCAN REPORT

MongoDB Atlas MCP Server

76 tools. 38 can modify or destroy data without limits.

11 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

38 can modify or destroy data

38 read-only

76 tools total

Community server · catalogue entry verified 29/06/2026

How to control MongoDB Atlas MCP Server ↓

TOOL MAP

What MongoDB Atlas MCP Server exposes to your agents

Read (38) Write / Execute (27) Destructive / Financial (11)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MongoDB Atlas MCP Server tools

Destructive · High cloud_provider_access_delete Deleting a cloud provider access role removes authentication/authorization credentials or role bindings permanently, which cannot be easily undone and could disrupt MongoDB Atlas operations or security posture. Destructive · Critical cluster_delete This tool irreversibly deletes an entire MongoDB cluster, destroying all data and backups associated with it. Destructive · High custom_db_role_delete Deleting a custom database role is an irreversible action that removes access control configurations. Destructive · Critical datalake_delete This tool performs an irreversible deletion operation on a Data Lake, which constitutes a destructive action with potentially massive blast radius.

38 of MongoDB Atlas MCP Server's 76 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MongoDB Atlas MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and MongoDB Atlas MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "atlas_search_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "alert_acknowledge": {
    "limits": [
      {
        "counter": "alert_acknowledge_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "alert_get": {
    "limits": [
      {
        "counter": "alert_get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MongoDB Atlas MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MONGODB ATLAS →

Instant setup, no code required.

FULL CATALOGUE

All 76 MongoDB Atlas MCP Server tools

DESTRUCTIVE 11 tools

Destructive atlas_search_delete Delete an Atlas Search index Destructive cloud_provider_access_delete Delete a cloud provider access role Destructive cluster_delete Delete a cluster Destructive custom_db_role_delete Delete a custom database role Destructive datalake_delete Delete a Data Lake Destructive organization_delete Delete an organization Destructive project_access_list_delete Delete an IP access list entry from the project Destructive project_delete Delete a project by ID Destructive project_remove_user Remove a user from a project Destructive project_whitelist_delete Delete an IP whitelist entry from the project (legacy) Destructive user_delete Delete a database user

EXECUTE 1 tools

Execute cluster_test_primary_failover Initiate a test primary failover for the cluster

WRITE 26 tools

Write alert_acknowledge Acknowledge an alert Write atlas_search_create Create a new Atlas Search index Write atlas_search_update Update an Atlas Search index Write atlas_search_upsert_analyzer Create or update Atlas Search analyzers for a cluster Write atlas_user_create Create an Atlas user Write atlas_user_update Update an Atlas user by ID Write cloud_backup_create_restore_job Create a snapshot restore job for a cluster Write cloud_provider_access_create Create a cloud provider access role Write cloud_provider_access_update Update a cloud provider access role Write cluster_create Create a new cluster Write cluster_update Update an existing cluster Write cluster_update_advanced_configuration Update advanced configuration (processArgs) for a cluster Write custom_db_role_create Create a custom database role Write custom_db_role_update Update a custom database role Write datalake_create Create a Data Lake Write datalake_update Update a Data Lake Write organization_invite Invite users to an organization Write organization_rename Rename an organization Write project_access_list_create Add IP addresses to the access list Write project_access_list_update Update IP access list entries for the project (POST semantics) Write project_assign_teams Assign teams to a project Write project_create Create a new project Write project_whitelist_create Add IP addresses to the whitelist (legacy) Write project_whitelist_update Update project whitelist entries (legacy) Write user_create Create a new database user Write user_update Update an existing database user

READ 38 tools

Read alert_get Get an alert by ID Read alert_get_all Get all alerts for the project Read atlas_search_get Get details for a specific Atlas Search index Read atlas_search_get_all Get all Atlas Search indexes for a cluster Read atlas_search_get_all_analyzers Get all Atlas Search analyzers for a cluster Read atlas_user_get_all Get all Atlas users for the project Read atlas_user_get_by_id Get Atlas user by ID Read atlas_user_get_by_name Get Atlas user by username Read cloud_backup_get_restore_job Get a specific snapshot restore job for a cluster Read cloud_backup_get_snapshot Get details of a specific snapshot Read cloud_backup_get_snapshots Get all cloud backup snapshots for a cluster Read cloud_provider_access_get_all Get all cloud provider access roles for the project Read cluster_get Get details of a specific cluster Read cluster_get_advanced_configuration Get advanced configuration (processArgs) for a cluster Read cluster_get_all Get all clusters in the project Read custom_db_role_get Get a custom database role by name Read custom_db_role_get_all Get all custom database roles Read datalake_get Get a Data Lake by name Read datalake_get_all Get all Data Lakes for the project Read datalake_get_logs_stream Get query logs (gzipped) for a Data Lake as base64-encoded gzip data Read events_get Get details of a specific event Read events_get_all Get all events for the project Read events_get_all_by_org Get all events for a specific organization Read events_get_by_org Get an event by ID for a specific organization Read organization_get_all Get all organizations Read organization_get_by_id Get organization details by ID Read organization_get_projects Get all projects for an organization Read organization_get_users Get all users for an organization Read project_access_list_get Get a specific access list entry for the project Read project_access_list_get_all Get all IP access list entries for the project Read project_get_all Get all projects Read project_get_by_id Get project details by ID Read project_get_by_name Get project details by name Read project_get_teams Get all teams for a given project ID Read project_whitelist_get Get a specific IP whitelist entry for the project (legacy) Read project_whitelist_get_all Get all IP whitelist entries for the project (legacy) Read user_get Get a specific database user by username Read user_get_all Get all database users

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MongoDB Atlas MCP Server

Can an AI agent delete data through the MongoDB Atlas MCP Server MCP server? +

Yes. The MongoDB Atlas MCP Server server exposes 11 destructive tools including atlas_search_delete, cloud_provider_access_delete, cluster_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MongoDB Atlas MCP Server? +

The MongoDB Atlas MCP Server server has 26 write tools including alert_acknowledge, atlas_search_create, atlas_search_update. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MongoDB Atlas MCP Server.

How many tools does the MongoDB Atlas MCP Server MCP server expose? +

76 tools across 3 categories: Destructive, Read, Write. 38 are read-only. 38 can modify, create, or delete data.

How do I enforce a policy on MongoDB Atlas MCP Server? +

Register the MongoDB Atlas MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MongoDB Atlas MCP Server tool call.

Deterministic rules across all 76 MongoDB Atlas MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MONGODB ATLAS →

Instant setup, no code required.

76 MongoDB Atlas MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.