Remove a user from a project
AI agents call n8n_remove_user_from_project to permanently remove resources in n8n MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a project is an irreversible access control action — the user loses project membership and associated permissions immediately. While the user account itself isn't deleted, the removal of project access is effectively destructive and not automatically reversible without re-adding the user manually.
From the tool's definition Remove a user from a project
Attacks that exploit this kind of access
Remove a user from a project. It is categorised as a Destructive tool in the n8n MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_remove_user_from_project: 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 n8n MCP Server. Nothing to install.
n8n_remove_user_from_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the n8n_remove_user_from_project 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 n8n_remove_user_from_project. 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.
n8n_remove_user_from_project is provided by the n8n MCP Server MCP server (shravan1610/n8n-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 →