list_atlas_clusters

THE RISK

Low Risk

Why list_atlas_clusters needs a policy

This tool retrieves information about existing MongoDB Atlas clusters. While it is a read-only operation with no side effects, it reveals sensitive infrastructure details (cluster names, configurations, status) that could be valuable for reconnaissance if an agent is compromised or operating under adversarial instructions.

From the tool's definition Tool name 'list_atlas_clusters' and description 'Lists all clusters in an Atlas project' indicate a query operation that retrieves data without modification.

Documented attack patterns abuse exactly the kind of access list_atlas_clusters gives an agent:

POLICY

How to control list_atlas_clusters

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. This is the rule we recommend for list_atlas_clusters:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_atlas_clusters": {}
  }
}

list_atlas_clusters is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MongoDB Atlas MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MongoDB Atlas MCP Server tools

Write create_atlas_cluster Creates a new Atlas cluster in an existing Atlas project. Write create_atlas_user Creates a new database user for an existing Atlas project. User will have atlasAdmin role. Write setup_atlas_network_access Sets up network access for an existing Atlas project. Accepts list of IP addresses or CIDR Read get_atlas_connection_strings Retrieves connection strings for a cluster in an existing Atlas project. Read list_atlas_projects Lists all Atlas projects that the API key has access to.

All 6 MongoDB Atlas MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_atlas_clusters

What does the list_atlas_clusters tool do? +

Lists all clusters in an Atlas project. It is categorised as a Read tool in the MongoDB Atlas MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_atlas_clusters? +

Register the MongoDB Atlas MCP Server MCP server in PolicyLayer and add a rule for list_atlas_clusters: 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 list_atlas_clusters? +

list_atlas_clusters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_atlas_clusters? +

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

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

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

Enforce policy on every MongoDB Atlas MCP Server tool call.

Start from MongoDB Atlas MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →