project_remove_user

Remove a user from a project

Server MongoDB Atlas MCP Server montumodi/mongodb-atlas-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What project_remove_user does on MongoDB Atlas MCP Server

AI agents call project_remove_user to permanently remove resources in MongoDB Atlas MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why project_remove_user needs a policy

This tool irreversibly removes a user's access to a project, which is a destructive action that alters authentication/authorization state and cannot be automatically reversed. While not data deletion per se, it permanently revokes user permissions and is categorized as Destructive due to its irreversible nature.

From the tool's definition Tool name 'project_remove_user' combined with description 'Remove a user from a project' indicates irreversible deletion of access control. The action 'remove' applied to a user assignment cannot be undone without explicit re-addition by an administrator.

Questions about project_remove_user

What does the project_remove_user tool do? +

Remove a user from a project. It is categorised as a Destructive tool in the MongoDB Atlas MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on project_remove_user? +

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

project_remove_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit project_remove_user? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.