neuron_respond_approval
Approve or reject a pending approval programmatically — the decision surface for an authorized operator acting via MCP instead of replying on WhatsApp. Fires the configured callback and posts the outcome to the WhatsApp chat. Exactly-once: the first responder (here or on WhatsApp) wins; later res...
This record as markdown: /tools/io-github-conquext-neuron/neuron-respond-approval.md
What neuron_respond_approval does on Neuron
AI agents use neuron_respond_approval 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 |
|---|---|---|---|
apiKey | string | Yes | Bot API key with 'nrn_' prefix for authentication |
reason | string | — | Optional reason (recommended for rejections) |
decision | string | Yes | The decision to record |
approvalId | string | Yes | The approval request id (UUID) |
responderName | string | — | Optional display name of the operator making the decision |
Parameters from the server's own tool schema.
Why neuron_respond_approval is rated Medium
An AI agent can call neuron_respond_approval faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs neuron_respond_approval 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_respond_approval, this is the rule to start with:
neuron_respond_approval 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_respond_approval call is checked against it from then on.
Questions about neuron_respond_approval
Approve or reject a pending approval programmatically — the decision surface for an authorized operator acting via MCP instead of replying on WhatsApp. Fires the configured callback and posts the outcome to the WhatsApp chat. Exactly-once: the first responder (here or on WhatsApp) wins; later responses return 410. Requires a bot API key. 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_respond_approval accepts 5 parameters: apiKey, reason, decision, approvalId, responderName. Required: apiKey, decision, approvalId. 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_respond_approval: 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_respond_approval 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_respond_approval 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_respond_approval. 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_respond_approval 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