neuron_list_contact_lists
Retrieve all contact lists for the current organization with optional filtering by search term, type, and pagination.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-contact-lists.md
What neuron_list_contact_lists does on Neuron
AI agents call neuron_list_contact_lists 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) |
type | string | — | Filter by list type: 'static', 'dynamic', or 'merged' |
limit | integer | — | Number of items per page (default: 20) |
search | string | — | Search term to filter lists by name or slug |
Parameters from the server's own tool schema.
Why neuron_list_contact_lists is rated Low
This tool retrieves and queries contact list metadata without creating, modifying, or deleting any data. The parameters mentioned (search term, type, pagination) are all read-only filtering mechanisms. There are no side effects on the data itself, making this a straightforward Read category tool with low severity since it only accesses organizational contact list information.
From the tool's definition Tool name contains 'list' and description states 'Retrieve all contact lists' with 'optional filtering by search term, type, and pagination' - all query/retrieval operations with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs neuron_list_contact_lists 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_list_contact_lists, this is the rule to start with:
neuron_list_contact_lists 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_list_contact_lists call is checked against it from then on.
Questions about neuron_list_contact_lists
Retrieve all contact lists for the current organization with optional filtering by search term, type, and pagination. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_contact_lists accepts 4 parameters: page, type, limit, search. 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_list_contact_lists: 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_list_contact_lists 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_list_contact_lists 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_list_contact_lists. 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_list_contact_lists 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