neuron_list_outbound_webhooks
Retrieve all outbound webhooks configured for a specific bot, including their target URLs and subscribed event types.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-outbound-webhooks.md
What neuron_list_outbound_webhooks does on Neuron
AI agents call neuron_list_outbound_webhooks to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
botId | string | Yes | Unique identifier (UUID) of the bot to list outbound webhooks for |
Parameters from the server's own tool schema.
Why neuron_list_outbound_webhooks is rated Low
The tool retrieves and queries existing webhook configuration data without creating, modifying, or deleting any resources. It has no side effects and poses minimal risk if invoked by an AI agent, as it only exposes information about webhook subscriptions that are already configured. The low severity reflects the read-only nature and limited blast radius.
From the tool's definition Tool name contains 'list' and description states 'Retrieve all outbound webhooks'—this is a query operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs neuron_list_outbound_webhooks 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_list_outbound_webhooks, this is the rule to start with:
neuron_list_outbound_webhooks is read-only, so it stays allowed. 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_list_outbound_webhooks call is checked against it from then on.
Questions about neuron_list_outbound_webhooks
Retrieve all outbound webhooks configured for a specific bot, including their target URLs and subscribed event types. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_outbound_webhooks accepts 1 parameter: botId. Required: 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_list_outbound_webhooks: 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_list_outbound_webhooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_list_outbound_webhooks 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_list_outbound_webhooks. 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_list_outbound_webhooks 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