neuron_create_outbound_webhook

Register a new outbound webhook that sends HTTP POST requests to an external URL when specified bot events occur. Supported events: message.created, message.assistant, conversation.created, conversation.escalated, conversation.closed, bot.paused, bot.resumed.

SERVERNeuron SOURCEneuron-mcp-server
Medium RISK CLASS
Category Write
Parameters 54 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-create-outbound-webhook.md

What neuron_create_outbound_webhook does on Neuron

AI agents use neuron_create_outbound_webhook 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.

ParameterTypeRequiredDescription
url string Yes Destination URL that will receive webhook event payloads (HTTPS recommended)
name string Yes Human-readable name for the outbound webhook
botId string Yes Unique identifier (UUID) of the bot to create the outbound webhook for
eventTypes array Yes Array of event types that should trigger this webhook
filterPrompt string Optional LLM prompt to selectively filter which events are forwarded (e.g., 'only forward escalations about billing')

Parameters from the server's own tool schema.

Why neuron_create_outbound_webhook is rated Medium

Creating an outbound webhook is a Write operation—it irreversibly establishes a new data structure (webhook registration) that causes the system to send sensitive bot event data to external URLs. While reversible (webhooks can be deleted), the action modifies system state and integrations.

From the tool's definition Tool description explicitly states 'Register a new outbound webhook' and 'sends HTTP POST requests to an external URL when specified bot events occur.' This creates a new persistent configuration that modifies system behavior by establishing external…

Risk signalsAccepts URL/endpoint input (url)

Questions about neuron_create_outbound_webhook

What does the neuron_create_outbound_webhook tool do? +

Register a new outbound webhook that sends HTTP POST requests to an external URL when specified bot events occur. Supported events: message.created, message.assistant, conversation.created, conversation.escalated, conversation.closed, bot.paused, bot.resumed. 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_create_outbound_webhook accept? +

neuron_create_outbound_webhook accepts 5 parameters: url, name, botId, eventTypes, filterPrompt. Required: url, name, botId, eventTypes. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_create_outbound_webhook? +

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

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

Can I rate-limit neuron_create_outbound_webhook? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Neuron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.