neuron_request_pair_code
Request a numeric pairing code for a Baileys channel as an alternative to QR code scanning. Requires the phone number to pair with.
This record as markdown: /tools/io-github-conquext-neuron/neuron-request-pair-code.md
What neuron_request_pair_code does on Neuron
AI agents invoke neuron_request_pair_code to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the Baileys channel |
phoneNumber | string | Yes | Phone number to generate the pair code for (E.164 format, e.g., '+2348012345678') |
Parameters from the server's own tool schema.
Why neuron_request_pair_code is rated High
This tool initiates an external operation (requesting a pairing code) that triggers an action on a remote WhatsApp channel/service. It is not a simple read, but rather executes an authentication/pairing workflow involving an external system. Misuse could allow unauthorized pairing of WhatsApp channels to attacker-controlled numbers.
From the tool's definition Request a numeric pairing code for a Baileys channel as an alternative to QR code scanning. Requires the phone number to pair with.
Attacks that exploit this kind of access
The rule that runs neuron_request_pair_code 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_request_pair_code, this is the rule to start with:
neuron_request_pair_code stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_request_pair_code call is checked against it from then on.
Questions about neuron_request_pair_code
Request a numeric pairing code for a Baileys channel as an alternative to QR code scanning. Requires the phone number to pair with. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_request_pair_code accepts 2 parameters: id, phoneNumber. Required: id, phoneNumber. 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_request_pair_code: 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_request_pair_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_request_pair_code 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_request_pair_code. 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_request_pair_code 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