neuron_delete_webhook
Permanently remove an inbound webhook from a bot. External services will no longer be able to trigger this endpoint.
This record as markdown: /tools/io-github-conquext-neuron/neuron-delete-webhook.md
What neuron_delete_webhook does on Neuron
AI agents call neuron_delete_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 webhook to delete |
Parameters from the server's own tool schema.
Why neuron_delete_webhook is rated Critical
This tool permanently deletes webhook infrastructure, which cannot be undone. Once removed, the webhook endpoint is destroyed and external service integrations are severed. This is a destructive operation with potential to disrupt bot functionality and break dependent integrations.
From the tool's definition Tool description states 'Permanently remove' and 'will no longer be able to trigger this endpoint', indicating irreversible deletion of webhook configuration.
Attacks that exploit this kind of access
The rule that runs neuron_delete_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_webhook, this is the rule to start with:
neuron_delete_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_webhook call is checked against it from then on.
Questions about neuron_delete_webhook
Permanently remove an inbound webhook from a bot. External services will no longer be able to trigger this endpoint. 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_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_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_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_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_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_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