neuron_handle_join_requests

Approve or reject pending join requests for a WhatsApp group. Requires admin privileges.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 44 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-handle-join-requests.md

WHAT IT DOES

What neuron_handle_join_requests does on Neuron

AI agents use neuron_handle_join_requests 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
`action`	string	Yes	Whether to approve or reject the join requests
`groupJid`	string	Yes	Group JID (ending in @g.us)
`channelId`	string	Yes	WhatsApp channel identifier (UUID)
`participants`	array	Yes	Array of phone numbers or JIDs of requesters

Parameters from the server's own tool schema.

RISK

Why neuron_handle_join_requests is rated Medium

This tool modifies group membership state by approving or rejecting join requests, which are write operations. Although it affects who can access a group, these decisions are not irreversible (admins can remove approved members or reinvite rejected ones), so it does not qualify as Destructive.

From the tool's definition Tool description states 'Approve or reject pending join requests' — these are reversible state changes (approval can be reversed by removal, rejection can be overturned by resubmitting a request).

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_handle_join_requests Rate-limited

neuron_handle_join_requests 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_handle_join_requests": {
      "limits": [
        {
          "counter": "neuron_handle_join_requests_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_handle_join_requests call is checked against it from then on.

FAQ

Questions about neuron_handle_join_requests

What does the neuron_handle_join_requests tool do? +

Approve or reject pending join requests for a WhatsApp group. Requires admin privileges. 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_handle_join_requests accept? +

neuron_handle_join_requests accepts 4 parameters: action, groupJid, channelId, participants. Required: action, groupJid, channelId, participants. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_handle_join_requests? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_handle_join_requests: 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_handle_join_requests? +

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

Can I rate-limit neuron_handle_join_requests? +

Yes. Add a rate_limit block to the neuron_handle_join_requests 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_handle_join_requests completely? +

Set action: deny in the PolicyLayer policy for neuron_handle_join_requests. 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_handle_join_requests? +

neuron_handle_join_requests 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

The MCP Attack Database →

Guides

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