neuron_update_contact_list

Update an existing contact list's name, slug, description, criteria, or refresh schedule.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-update-contact-list.md

WHAT IT DOES

What neuron_update_contact_list does on Neuron

AI agents use neuron_update_contact_list to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.

Parameter	Type	Required	Description
`name`	string	—	Updated display name for the list
`slug`	string	—	Updated URL-friendly slug for the list
`criteria`	object	—	Updated dynamic list criteria. Set to null to clear existing criteria.
`idOrSlug`	string	Yes	Unique identifier (UUID) or URL-friendly slug of the contact list to update
`description`	string	—	Updated description of the list's purpose
`refreshSchedule`	string	—	Updated refresh schedule for dynamic lists

Parameters from the server's own tool schema.

RISK

Why neuron_update_contact_list is rated Medium

This tool modifies existing data (contact list properties) reversibly without deleting, destroying, or executing arbitrary code. The changes (name, slug, description, criteria, refresh schedule) are all editable fields that can be reverted. While contact lists in a chatbot platform could have business importance, the operation itself is a standard write/update action with no destructive or execute semantics.

From the tool's definition Tool name and description indicate 'Update' operation on contact list attributes: 'name, slug, description, criteria, or refresh schedule' — these are reversible modifications to metadata and configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_update_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_update_contact_list, this is the rule to start with:

neuron_update_contact_list Rate-limited

neuron_update_contact_list stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_contact_list": {
      "limits": [
        {
          "counter": "neuron_update_contact_list_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_update_contact_list call is checked against it from then on.

FAQ

Questions about neuron_update_contact_list

What does the neuron_update_contact_list tool do? +

Update an existing contact list's name, slug, description, criteria, or refresh schedule. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does neuron_update_contact_list accept? +

neuron_update_contact_list accepts 6 parameters: name, slug, criteria, idOrSlug, description, refreshSchedule. Required: idOrSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_update_contact_list? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_update_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.

What risk level is neuron_update_contact_list? +

neuron_update_contact_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_contact_list? +

Yes. Add a rate_limit block to the neuron_update_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.

How do I block neuron_update_contact_list completely? +

Set action: deny in the PolicyLayer policy for neuron_update_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.

What MCP server provides neuron_update_contact_list? +

neuron_update_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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 231 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →