neuron_get_contact_list_members
Retrieve the members of a specific contact list with optional search filtering and pagination.
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-contact-list-members.md
What neuron_get_contact_list_members does on Neuron
AI agents call neuron_get_contact_list_members 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) |
search | string | — | Search term to filter members by name or phone number |
idOrSlug | string | Yes | Unique identifier (UUID) or URL-friendly slug of the contact list |
Parameters from the server's own tool schema.
Why neuron_get_contact_list_members is rated Low
This tool retrieves contact list membership data. It performs a query operation with no capability to modify, delete, or execute actions. The presence of filtering and pagination are standard read-operation features. No financial, destructive, or code execution risk is present.
From the tool's definition Tool name includes 'get' and description states 'Retrieve the members' with 'search filtering and pagination' — all read operations that query data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs neuron_get_contact_list_members 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_get_contact_list_members, this is the rule to start with:
neuron_get_contact_list_members 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_get_contact_list_members call is checked against it from then on.
Questions about neuron_get_contact_list_members
Retrieve the members of a specific contact list with optional search filtering and pagination. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_contact_list_members accepts 4 parameters: page, limit, search, 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_get_contact_list_members: 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_get_contact_list_members 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_get_contact_list_members 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_get_contact_list_members. 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_get_contact_list_members 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