neuron_delete_outbound_webhook
Permanently remove an outbound webhook. The external endpoint will no longer receive event notifications from this bot.
This record as markdown: /tools/io-github-conquext-neuron/neuron-delete-outbound-webhook.md
What neuron_delete_outbound_webhook does on Neuron
AI agents call neuron_delete_outbound_webhook to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the outbound webhook to delete |
Parameters from the server's own tool schema.
Why neuron_delete_outbound_webhook is rated Critical
This tool irreversibly deletes a webhook configuration and cannot be undone without manual reconfiguration. While the data loss is limited to the webhook endpoint itself (not bulk customer data), the permanent deletion of configured integrations qualifies as a Destructive operation.
From the tool's definition Tool description explicitly states 'Permanently remove' an outbound webhook. The term 'permanently' indicates an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs neuron_delete_outbound_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_delete_outbound_webhook, this is the rule to start with:
neuron_delete_outbound_webhook is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_delete_outbound_webhook call is checked against it from then on.
Questions about neuron_delete_outbound_webhook
Permanently remove an outbound webhook. The external endpoint will no longer receive event notifications from this bot. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_delete_outbound_webhook accepts 1 parameter: id. Required: id. 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_delete_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.
neuron_delete_outbound_webhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neuron_delete_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.
Set action: deny in the PolicyLayer policy for neuron_delete_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.
neuron_delete_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.
Across the catalogue