neuron_refresh_contact_list
Trigger a refresh of a dynamic contact list. Re-evaluates criteria rules and/or AI prompt and materializes updated members.
This record as markdown: /tools/io-github-conquext-neuron/neuron-refresh-contact-list.md
What neuron_refresh_contact_list does on Neuron
AI agents invoke neuron_refresh_contact_list to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
idOrSlug | string | Yes | Unique identifier (UUID) or URL-friendly slug of the dynamic list to refresh |
Parameters from the server's own tool schema.
Why neuron_refresh_contact_list is rated High
This tool triggers an external operation (re-evaluation of criteria/AI prompt and materialization of contact list members). It doesn't simply read data, nor does it irreversibly delete anything — it executes a refresh/re-computation process that modifies the membership of a contact list based on dynamic rules.
From the tool's definition Trigger a refresh of a dynamic contact list. Re-evaluates criteria rules and/or AI prompt and materializes updated members.
Attacks that exploit this kind of access
The rule that runs neuron_refresh_contact_list 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_contact_list, this is the rule to start with:
neuron_refresh_contact_list stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_contact_list call is checked against it from then on.
Questions about neuron_refresh_contact_list
Trigger a refresh of a dynamic contact list. Re-evaluates criteria rules and/or AI prompt and materializes updated members. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_refresh_contact_list accepts 1 parameter: idOrSlug. Required: idOrSlug. 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_contact_list: 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_contact_list is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_refresh_contact_list 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_contact_list. 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_contact_list 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