neuron_update_member

Update a member's permissions within the organization, such as conversation access. Only provided fields are changed.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-update-member.md

WHAT IT DOES

What neuron_update_member does on Neuron

AI agents use neuron_update_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
`orgId`	string	Yes	Unique identifier (UUID) of the organization
`userId`	string	Yes	Unique identifier (UUID) of the member to update
`canViewConversations`	boolean	Yes	Whether the member can view conversations

Parameters from the server's own tool schema.

RISK

Why neuron_update_member is rated Medium

This tool modifies (updates) member permissions and access control settings reversibly. It does not delete data or trigger external operations, making it a Write action. The severity is medium because granting or revoking inappropriate permissions could impact organizational security and member access, but the change is reversible and does not directly destroy data or execute code.

From the tool's definition Tool description states 'Update a member's permissions within the organization, such as conversation access. Only provided fields are changed.' This is a modification operation that changes user permissions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_update_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_update_member, this is the rule to start with:

neuron_update_member Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_member": {
      "limits": [
        {
          "counter": "neuron_update_member_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_update_member call is checked against it from then on.

FAQ

Questions about neuron_update_member

What does the neuron_update_member tool do? +

Update a member's permissions within the organization, such as conversation access. Only provided fields are changed. 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.

What parameters does neuron_update_member accept? +

neuron_update_member accepts 3 parameters: orgId, userId, canViewConversations. Required: orgId, userId, canViewConversations. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_update_member? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_update_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.

What risk level is neuron_update_member? +

neuron_update_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_member? +

Yes. Add a rate_limit block to the neuron_update_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.

How do I block neuron_update_member completely? +

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

What MCP server provides neuron_update_member? +

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

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 231 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →