neuron_semantic_search_contacts
Search contacts using natural language AI-powered semantic search. Finds contacts based on the meaning of their notes — skills, services, schedules, preferences, etc. Returns ranked results with relevance scores and AI-generated match reasons.
This record as markdown: /tools/io-github-conquext-neuron/neuron-semantic-search-contacts.md
What neuron_semantic_search_contacts does on Neuron
AI agents call neuron_semantic_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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (default: 10, max: 20) |
query | string | Yes | Natural language search query (e.g., 'who can deliver to Lagos on Monday?') |
Parameters from the server's own tool schema.
Why neuron_semantic_search_contacts is rated Low
This tool retrieves and queries existing contact data based on semantic criteria. It does not create, modify, delete, execute code, or move money. The operation is purely informational with no side effects on the contact records themselves.
From the tool's definition The tool performs semantic search to find contacts using natural language AI; returns ranked results with relevance scores and match reasons. Keywords indicating query/retrieval operation: 'search', 'finds', 'returns ranked results'.
Attacks that exploit this kind of access
The rule that runs neuron_semantic_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_semantic_search_contacts, this is the rule to start with:
neuron_semantic_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_semantic_search_contacts call is checked against it from then on.
Questions about neuron_semantic_search_contacts
Search contacts using natural language AI-powered semantic search. Finds contacts based on the meaning of their notes — skills, services, schedules, preferences, etc. Returns ranked results with relevance scores and AI-generated match reasons. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_semantic_search_contacts accepts 2 parameters: limit, query. Required: query. 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_semantic_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_semantic_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_semantic_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_semantic_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_semantic_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