neuron_refresh_newsletter
Re-fetch metadata (name, description, subscriber count) for a WhatsApp Channel newsletter from WhatsApp to synchronize local data.
This record as markdown: /tools/io-github-conquext-neuron/neuron-refresh-newsletter.md
What neuron_refresh_newsletter does on Neuron
AI agents call neuron_refresh_newsletter 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 newsletter to refresh |
Parameters from the server's own tool schema.
Why neuron_refresh_newsletter is rated Low
This tool performs a read-only operation: it queries WhatsApp for newsletter metadata and updates local cache/state to keep it in sync. It does not create, modify, delete, or execute arbitrary operations. The worst-case scenario is stale or inconsistent metadata, which poses minimal risk. Confidence is high because the description clearly indicates metadata retrieval only.
From the tool's definition Tool re-fetches and synchronizes metadata (name, description, subscriber count) from WhatsApp—a retrieval and synchronization operation with no data modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs neuron_refresh_newsletter 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_refresh_newsletter, this is the rule to start with:
neuron_refresh_newsletter 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_refresh_newsletter call is checked against it from then on.
Questions about neuron_refresh_newsletter
Re-fetch metadata (name, description, subscriber count) for a WhatsApp Channel newsletter from WhatsApp to synchronize local data. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_refresh_newsletter 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_refresh_newsletter: 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_refresh_newsletter 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_refresh_newsletter 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_refresh_newsletter. 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_refresh_newsletter 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