neuron_create_contact_list

Create a new contact list. Slug is auto-generated from name if not provided. For dynamic lists, provide criteria with rules and/or an AI prompt.

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-create-contact-list.md

WHAT IT DOES

What neuron_create_contact_list does on Neuron

AI agents use neuron_create_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	Yes	Display name for the contact list
`slug`	string	—	URL-friendly identifier (auto-generated from name if omitted)
`type`	string	—	List type (default: 'static')
`criteria`	object	—	Dynamic list criteria object: { rules?: { operator, conditions }, aiPrompt?, aiMaxResults? }
`description`	string	—	Human-readable description of the list's purpose
`refreshSchedule`	string	—	Refresh schedule for dynamic lists (default: 'manual')

Parameters from the server's own tool schema.

RISK

Why neuron_create_contact_list is rated Medium

This tool creates a new contact list, which is a reversible write operation. It modifies the system state by adding a new resource (contact list) but does not delete, execute code, move money, or produce irreversible changes. The ability to auto-generate slugs and define dynamic list criteria via rules/AI prompts represents configuration of data structures rather than destructive or executable operations.

From the tool's definition Tool name 'neuron_create_contact_list' and description 'Create a new contact list' explicitly indicates creation of new data structure.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_create_contact_list Rate-limited

neuron_create_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_create_contact_list": {
      "limits": [
        {
          "counter": "neuron_create_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_create_contact_list call is checked against it from then on.

FAQ

Questions about neuron_create_contact_list

What does the neuron_create_contact_list tool do? +

Create a new contact list. Slug is auto-generated from name if not provided. For dynamic lists, provide criteria with rules and/or an AI prompt. 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_create_contact_list accept? +

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

How do I enforce a policy on neuron_create_contact_list? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_create_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_create_contact_list? +

neuron_create_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_create_contact_list? +

Yes. Add a rate_limit block to the neuron_create_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_create_contact_list completely? +

Set action: deny in the PolicyLayer policy for neuron_create_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_create_contact_list? +

neuron_create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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