neuron_register
Register a new user account with name, email, password, and organization name. Creates both the user and an initial organization.
This record as markdown: /tools/io-github-conquext-neuron/neuron-register.md
What neuron_register does on Neuron
AI agents use neuron_register 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 user |
email | string | Yes | Email address for the new account |
orgName | string | Yes | Name of the organization to create for this user |
password | string | Yes | Password for the account (minimum 8 characters) |
Parameters from the server's own tool schema.
Why neuron_register is rated Medium
This tool creates new user accounts and organizations, which is a Write operation (data creation). Severity is high because unauthorized account creation could enable account takeover, privilege escalation, or unauthorized access to the WhatsApp chatbot platform and its 196 tools.
From the tool's definition Tool description states it 'Register a new user account' and 'Creates both the user and an initial organization', indicating reversible creation of user and organizational data.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs neuron_register 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_register, this is the rule to start with:
neuron_register 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_register call is checked against it from then on.
Questions about neuron_register
Register a new user account with name, email, password, and organization name. Creates both the user and an initial organization. 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_register accepts 4 parameters: name, email, orgName, password. Required: name, email, orgName, password. 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_register: 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_register 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_register 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_register. 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_register 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