neuron_create_webhook
Register a new inbound webhook endpoint that triggers bot actions when called by an external service.
This record as markdown: /tools/io-github-conquext-neuron/neuron-create-webhook.md
What neuron_create_webhook does on Neuron
AI agents use neuron_create_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Human-readable name for the webhook |
slug | string | — | URL-friendly slug for the webhook endpoint (auto-generated if omitted) |
botId | string | Yes | Unique identifier (UUID) of the bot to create the webhook for |
isActive | boolean | — | Whether the webhook is active and accepting requests (default: true) |
eventType | string | — | Type of event this webhook handles (e.g., 'order.created', 'payment.received') |
processingPrompt | string | — | Prompt instructions to guide bot processing of incoming webhook data |
Parameters from the server's own tool schema.
Why neuron_create_webhook is rated Medium
Creating a webhook endpoint is a reversible Write action that establishes new integrations and configurations. Severity is high because a malicious webhook could be registered to trigger unintended bot actions (spam campaigns, data exfiltration, contact manipulation) when called by external services, though the actual damage depends on what those triggered actions do.
From the tool's definition Tool description states 'Register a new inbound webhook endpoint' - registration is a create operation that persists configuration. The webhook 'triggers bot actions' indicating automation setup.
Attacks that exploit this kind of access
The rule that runs neuron_create_webhook 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_create_webhook, this is the rule to start with:
neuron_create_webhook 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_create_webhook call is checked against it from then on.
Questions about neuron_create_webhook
Register a new inbound webhook endpoint that triggers bot actions when called by an external service. 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_create_webhook accepts 6 parameters: name, slug, botId, isActive, eventType, processingPrompt. Required: name, botId. 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_create_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.
neuron_create_webhook 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_create_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.
Set action: deny in the PolicyLayer policy for neuron_create_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.
neuron_create_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.
This server
Across the catalogue