neuron_get_contact_list
Retrieve detailed information about a specific contact list, including member count and configuration.
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-contact-list.md
What neuron_get_contact_list does on Neuron
AI agents call neuron_get_contact_list 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 |
|---|---|---|---|
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 is rated Low
This tool retrieves contact list information without modifying, deleting, or executing any operations. It is purely a data query operation that has no side effects beyond fetching existing configuration details. The blast radius of misuse is minimal—an attacker could enumerate contact lists but not manipulate them.
From the tool's definition Tool name contains 'get' and description states 'Retrieve detailed information about a specific contact list, including member count and configuration.' The verb 'retrieve' and the read-only nature of querying contact list metadata indicate no data…
Attacks that exploit this kind of access
The rule that runs neuron_get_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_get_contact_list, this is the rule to start with:
neuron_get_contact_list 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 call is checked against it from then on.
Questions about neuron_get_contact_list
Retrieve detailed information about a specific contact list, including member count and configuration. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_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_get_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_get_contact_list 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 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. 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 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