neuron_list_leads

List leads from the pool, filterable by status (new/enriched/contacted/converted/rejected), sourceId, and search.

SERVERNeuron SOURCEneuron-mcp-server

Low RISK CLASS

Category Read

Parameters 50 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-list-leads.md

WHAT IT DOES

What neuron_list_leads does on Neuron

AI agents call neuron_list_leads 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
`page`	integer	—
`limit`	integer	—
`search`	string	—
`status`	string	—
`sourceId`	string	—

Parameters from the server's own tool schema.

RISK

Why neuron_list_leads is rated Low

Even though neuron_list_leads only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_list_leads Allowed

neuron_list_leads is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_list_leads": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_list_leads call is checked against it from then on.

FAQ

Questions about neuron_list_leads

What does the neuron_list_leads tool do? +

List leads from the pool, filterable by status (new/enriched/contacted/converted/rejected), sourceId, and search. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.

What parameters does neuron_list_leads accept? +

neuron_list_leads accepts 5 parameters: page, limit, search, status, sourceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_list_leads? +

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

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

Can I rate-limit neuron_list_leads? +

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

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

neuron_list_leads 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 281 Neuron tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →