neuron_get_outbound_webhook_logs
Retrieve delivery logs for an outbound webhook to monitor event dispatch history and debug delivery failures.
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-outbound-webhook-logs.md
What neuron_get_outbound_webhook_logs does on Neuron
AI agents call neuron_get_outbound_webhook_logs 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 |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the outbound webhook to get logs for |
page | number | — | Page number for pagination (default: 1) |
limit | number | — | Number of log entries per page (default: 20) |
Parameters from the server's own tool schema.
Why neuron_get_outbound_webhook_logs is rated Low
This tool retrieves historical data about webhook delivery attempts without any capability to create, modify, delete, or execute actions. It poses minimal security risk as it only provides visibility into past events for diagnostics and monitoring purposes.
From the tool's definition The tool name includes 'get' and the description states 'Retrieve delivery logs' — these are explicit read operations with no modification capability. The purpose is to 'monitor' and 'debug', which are passive inspection activities.
Attacks that exploit this kind of access
The rule that runs neuron_get_outbound_webhook_logs 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_get_outbound_webhook_logs, this is the rule to start with:
neuron_get_outbound_webhook_logs 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_get_outbound_webhook_logs call is checked against it from then on.
Questions about neuron_get_outbound_webhook_logs
Retrieve delivery logs for an outbound webhook to monitor event dispatch history and debug delivery failures. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_outbound_webhook_logs accepts 3 parameters: id, page, limit. 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_get_outbound_webhook_logs: 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_get_outbound_webhook_logs 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_get_outbound_webhook_logs 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_get_outbound_webhook_logs. 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_get_outbound_webhook_logs 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