Get a custom database role by name
AI agents call custom_db_role_get to retrieve information from MongoDB Atlas MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries MongoDB Atlas for a custom database role. It has no side effects, does not modify data, and cannot be exploited to cause damage through misuse. The blast radius of an AI agent using this tool is minimal—it can only retrieve information about role definitions that may already be accessible to the authenticated user.
From the tool's definition Tool name 'get' and description 'Get a custom database role by name' indicate data retrieval without modification. The function retrieves an existing database role configuration.
Attacks that exploit this kind of access
Get a custom database role by name. It is categorised as a Read tool in the MongoDB Atlas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MongoDB Atlas MCP Server MCP server in PolicyLayer and add a rule for custom_db_role_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the custom_db_role_get 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_get. 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_get 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 →