Update an Atlas user by ID
AI agents use atlas_user_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.
The tool modifies user attributes (likely password, roles, permissions, email, etc.) but does not delete users or irreversibly destroy data. In the context of Atlas (a managed database service), updating user credentials or permissions can impact access control and service configuration. However, the change is reversible through subsequent updates.
From the tool's definition Tool name 'atlas_user_update' and description 'Update an Atlas user by ID' indicate modification of user data. This is a reversible change operation typical of Write category tools.
Attacks that exploit this kind of access
Update an Atlas user by ID. 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 atlas_user_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.
atlas_user_update 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 atlas_user_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.
Set action: deny in the PolicyLayer policy for atlas_user_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.
atlas_user_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.
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 →