Create a custom database role
AI agents use custom_db_role_create 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.
The tool creates a new database role, which is a reversible write operation that modifies the authorization structure of MongoDB Atlas. While it grants access and can impact security posture, it is not destructive (can be deleted), not financial, and not directly executable code.
From the tool's definition Tool name contains 'create' and description states 'Create a custom database role'. This creates a new role entity in MongoDB Atlas that persists in the system.
Attacks that exploit this kind of access
Create 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.
Register the MongoDB Atlas MCP Server MCP server in PolicyLayer and add a rule for custom_db_role_create: 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.
custom_db_role_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the custom_db_role_create 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.
Set action: deny in the PolicyLayer policy for custom_db_role_create. 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.
custom_db_role_create 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →