neuron_get_eligible_contacts

Retrieve contacts eligible to receive a campaign message. Respects deduplication rules and mutual contact requirements.

SERVERNeuron SOURCEneuron-mcp-server
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-get-eligible-contacts.md

What neuron_get_eligible_contacts does on Neuron

AI agents call neuron_get_eligible_contacts 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.

ParameterTypeRequiredDescription
id string Yes Unique identifier (UUID) of the campaign to check eligibility for

Parameters from the server's own tool schema.

Why neuron_get_eligible_contacts is rated Low

This tool queries/retrieves contact eligibility data for campaign purposes. It applies filtering logic (deduplication rules, mutual contact requirements) but does not create, modify, delete, or execute external operations. The blast radius of misuse is limited to information disclosure about which contacts are eligible for messaging — no financial, destructive, or executable consequences.

From the tool's definition Tool name contains 'get' and description states 'Retrieve contacts eligible to receive a campaign message' — both indicate data retrieval with no modification or side effects.

Questions about neuron_get_eligible_contacts

What does the neuron_get_eligible_contacts tool do? +

Retrieve contacts eligible to receive a campaign message. Respects deduplication rules and mutual contact requirements. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.

What parameters does neuron_get_eligible_contacts accept? +

neuron_get_eligible_contacts accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_get_eligible_contacts? +

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

neuron_get_eligible_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit neuron_get_eligible_contacts? +

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

Set action: deny in the PolicyLayer policy for neuron_get_eligible_contacts. 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_get_eligible_contacts? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Neuron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.