neuron_bot_api_chat
Send a message to a bot via the API and receive a streaming or complete AI-generated response. Requires a valid API key with 'nrn_' prefix.
This record as markdown: /tools/io-github-conquext-neuron/neuron-bot-api-chat.md
What neuron_bot_api_chat does on Neuron
AI agents invoke neuron_bot_api_chat 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 |
|---|---|---|---|
apiKey | string | Yes | Bot API key with 'nrn_' prefix for authentication |
message | string | Yes | The message text to send to the bot |
contactName | string | — | Display name of the contact for conversation context |
contactPhone | string | Yes | Phone number of the contact sending the message (E.164 format, e.g., '+2348012345678') |
Parameters from the server's own tool schema.
Why neuron_bot_api_chat is rated High
This tool triggers an AI-generated response by sending a message to a bot, which constitutes executing an external operation with effects that depend on the arguments. The response is AI-generated and could cause downstream actions in the WhatsApp chatbot platform. Misuse could result in unintended messages being sent or AI operations being triggered at scale across contacts/campaigns.
From the tool's definition Send a message to a bot via the API and receive a streaming or complete AI-generated response
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs neuron_bot_api_chat 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_bot_api_chat, this is the rule to start with:
neuron_bot_api_chat 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_bot_api_chat call is checked against it from then on.
Questions about neuron_bot_api_chat
Send a message to a bot via the API and receive a streaming or complete AI-generated response. Requires a valid API key with 'nrn_' prefix. 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_bot_api_chat accepts 4 parameters: apiKey, message, contactName, contactPhone. Required: apiKey, message, contactPhone. 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_bot_api_chat: 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_bot_api_chat 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_bot_api_chat 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_bot_api_chat. 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_bot_api_chat 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