neuron_search_contacts
Search contacts by a query string across name, phone number, and email fields. Returns matching contacts ranked by relevance.
This record as markdown: /tools/io-github-conquext-neuron/neuron-search-contacts.md
What neuron_search_contacts does on Neuron
AI agents call neuron_search_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Search query string to match against contact name, phone, or email |
Parameters from the server's own tool schema.
Why neuron_search_contacts is rated Low
This tool retrieves and queries existing contact information based on search criteria. It has no side effects—it does not create, modify, delete, or execute any operations. The search functionality is inherently read-only and falls squarely within the Read category. Severity is low because contact search is a standard data retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool performs a search operation across contact data fields (name, phone number, email) and returns matching results. The description uses "search" and "returns matching contacts" which indicates data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs neuron_search_contacts 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_search_contacts, this is the rule to start with:
neuron_search_contacts 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_search_contacts call is checked against it from then on.
Questions about neuron_search_contacts
Search contacts by a query string across name, phone number, and email fields. Returns matching contacts ranked by relevance. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_search_contacts accepts 1 parameter: q. Required: q. 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_search_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.
neuron_search_contacts 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_search_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.
Set action: deny in the PolicyLayer policy for neuron_search_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.
neuron_search_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.
This server
Across the catalogue