neuron_remove_member
Permanently remove a member from the organization. The member loses all access immediately. This action cannot be undone.
This record as markdown: /tools/io-github-conquext-neuron/neuron-remove-member.md
What neuron_remove_member does on Neuron
AI agents call neuron_remove_member to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | Yes | Unique identifier (UUID) of the organization |
userId | string | Yes | Unique identifier (UUID) of the member to remove |
Parameters from the server's own tool schema.
Why neuron_remove_member is rated Critical
This tool irreversibly removes a member's access to the organization, which is a destructive action that cannot be reversed. While not a direct data deletion, it destroys a member's organizational authorization state permanently. The high severity reflects that misuse could lock out legitimate users from critical business operations on a WhatsApp chatbot platform used for campaigns and bots.
From the tool's definition Tool description explicitly states: 'Permanently remove a member from the organization. The member loses all access immediately.
Attacks that exploit this kind of access
The rule that runs neuron_remove_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_remove_member, this is the rule to start with:
neuron_remove_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_remove_member call is checked against it from then on.
Questions about neuron_remove_member
Permanently remove a member from the organization. The member loses all access immediately. This action cannot be undone. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_remove_member accepts 2 parameters: orgId, userId. Required: orgId, userId. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_remove_member: 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 Neuron. Nothing to install.
neuron_remove_member 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 neuron_remove_member 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 neuron_remove_member. 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.
neuron_remove_member is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue