Get Atlas user by username
AI agents call atlas_user_get_by_name 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 retrieves user information by username from MongoDB Atlas. It performs a simple lookup query with no capability to modify, delete, or execute operations. The blast radius of misuse is limited to information disclosure about user accounts, which is a low-severity concern in the context of Atlas management.
From the tool's definition Tool name 'atlas_user_get_by_name' and description 'Get Atlas user by username' indicate a retrieval operation with no side effects. The verb 'Get' is explicitly a read operation that queries user data without modification.
Attacks that exploit this kind of access
Get Atlas user by username. 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 atlas_user_get_by_name: 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.
atlas_user_get_by_name 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 atlas_user_get_by_name 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 atlas_user_get_by_name. 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.
atlas_user_get_by_name 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 →