neuron_invite_member
Send an invitation to a new member to join the organization. The invitee receives an email with a link to accept.
This record as markdown: /tools/io-github-conquext-neuron/neuron-invite-member.md
What neuron_invite_member does on Neuron
AI agents use neuron_invite_member to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Full name of the person being invited |
role | string | — | Role to assign to the member (e.g., 'admin', 'agent', 'viewer') |
email | string | Yes | Email address of the person to invite |
orgId | string | Yes | Unique identifier (UUID) of the organization |
canViewConversations | boolean | — | Whether the invited member can view conversations (default: true) |
Parameters from the server's own tool schema.
Why neuron_invite_member is rated Medium
This tool creates and sends data (an invitation and email) rather than retrieving, executing arbitrary code, destroying data, or moving money. However, it has moderate severity because mass invitations could spam users or be used for social engineering, and inviting unauthorized people could compromise organizational access.
From the tool's definition The tool "Send an invitation to a new member to join the organization. The invitee receives an email with a link to accept" performs a write operation that creates a new invitation record and sends an outbound email notification.
Attacks that exploit this kind of access
The rule that runs neuron_invite_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_invite_member, this is the rule to start with:
neuron_invite_member stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_invite_member call is checked against it from then on.
Questions about neuron_invite_member
Send an invitation to a new member to join the organization. The invitee receives an email with a link to accept. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_invite_member accepts 5 parameters: name, role, email, orgId, canViewConversations. Required: name, email, orgId. 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_invite_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_invite_member 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 neuron_invite_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_invite_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_invite_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.
This server
Across the catalogue