neuron_export_contacts
Export all contacts as a downloadable dataset for the current organization.
This record as markdown: /tools/io-github-conquext-neuron/neuron-export-contacts.md
What neuron_export_contacts does on Neuron
AI agents call neuron_export_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.
Why neuron_export_contacts is rated Low
This tool retrieves and exports contact data without modifying or deleting anything. However, it has medium severity because it exposes the entire organization's contact list as a bulk download, which could be a significant data privacy risk if misused by an AI agent.
From the tool's definition Export all contacts as a downloadable dataset
Attacks that exploit this kind of access
The rule that runs neuron_export_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_export_contacts, this is the rule to start with:
neuron_export_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_export_contacts call is checked against it from then on.
Questions about neuron_export_contacts
Export all contacts as a downloadable dataset for the current organization. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_export_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_export_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_export_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_export_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_export_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