cluster_test_primary_failover · MongoDB Atlas MCP Server MCP

WHAT IT DOES

What cluster_test_primary_failover does on MongoDB Atlas MCP Server

AI agents invoke cluster_test_primary_failover to trigger actions in MongoDB Atlas MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cluster_test_primary_failover needs a policy

This tool triggers an external operation (primary failover) on a live MongoDB cluster. While described as a 'test' failover, it actually initiates a real failover event that causes a primary node election, resulting in temporary unavailability and potential disruption to production workloads. It is not a read or simple write — it executes a disruptive cluster operation.

From the tool's definition Initiate a test primary failover for the cluster

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cluster_test_primary_failover Rate-limited

cluster_test_primary_failover stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cluster_test_primary_failover": {
      "limits": [
        {
          "counter": "cluster_test_primary_failover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 cluster_test_primary_failover

What does the cluster_test_primary_failover tool do? +

Initiate a test primary failover for the cluster. It is categorised as a Execute tool in the MongoDB Atlas MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cluster_test_primary_failover? +

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

cluster_test_primary_failover is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cluster_test_primary_failover? +

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

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

cluster_test_primary_failover 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.