neuron_list_newsletters
Retrieve a paginated list of all WhatsApp Channel newsletters for the organization, with optional filtering by WhatsApp session channel.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-newsletters.md
What neuron_list_newsletters does on Neuron
AI agents call neuron_list_newsletters 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default: 1) |
limit | integer | — | Number of items per page (default: 20) |
channelId | string | — | Filter newsletters by WhatsApp session channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_list_newsletters is rated Low
This tool retrieves organizational data (WhatsApp Channel newsletters) without modifying, deleting, or executing any operations. It performs simple querying and filtering on existing data. The blast radius of misuse is minimal—an attacker could view newsletters but cannot create, modify, delete, or cause financial harm. This is a standard read-only data access operation.
From the tool's definition Tool description states 'Retrieve a paginated list' of newsletters, which is a data retrieval operation with no side effects. The verb 'Retrieve' and the structure 'list...newsletters' are characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs neuron_list_newsletters 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_newsletters, this is the rule to start with:
neuron_list_newsletters 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_newsletters call is checked against it from then on.
Questions about neuron_list_newsletters
Retrieve a paginated list of all WhatsApp Channel newsletters for the organization, with optional filtering by WhatsApp session channel. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_newsletters accepts 3 parameters: page, limit, channelId. 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_newsletters: 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_newsletters 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_newsletters 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_newsletters. 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_newsletters 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