custom_db_role_update · MongoDB Atlas MCP Server MCP

WHAT IT DOES

What custom_db_role_update does on MongoDB Atlas MCP Server

AI agents use custom_db_role_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 custom_db_role_update needs a policy

This tool modifies database role definitions, which control permissions and access. While updates are typically reversible, misconfiguration could grant or revoke permissions unintentionally, affecting database access and security posture across multiple users.

From the tool's definition Tool name 'custom_db_role_update' and description 'Update a custom database role' indicate modification of access control roles. The 'update' action is inherently reversible, placing this in Write category rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_db_role_update Rate-limited

custom_db_role_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": {
    "custom_db_role_update": {
      "limits": [
        {
          "counter": "custom_db_role_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 custom_db_role_update

What does the custom_db_role_update tool do? +

Update a custom database role. 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 custom_db_role_update? +

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

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

Can I rate-limit custom_db_role_update? +

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

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

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