neuron_campaign_participants
Retrieve all participants who have joined a campaign you own, including their delivery counts and earned rewards.
This record as markdown: /tools/io-github-conquext-neuron/neuron-campaign-participants.md
What neuron_campaign_participants does on Neuron
AI agents call neuron_campaign_participants 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 |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the campaign you own |
Parameters from the server's own tool schema.
Why neuron_campaign_participants is rated Low
This tool queries and returns data about campaign participants, their delivery counts, and rewards. It performs no mutations, deletions, executions, or financial operations. The retrieval of campaign metadata poses minimal risk even if misused, as it only exposes information about campaigns the user already owns.
From the tool's definition Tool name 'neuron_campaign_participants' and description 'Retrieve all participants' — the verb 'Retrieve' indicates a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs neuron_campaign_participants 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_campaign_participants, this is the rule to start with:
neuron_campaign_participants 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_campaign_participants call is checked against it from then on.
Questions about neuron_campaign_participants
Retrieve all participants who have joined a campaign you own, including their delivery counts and earned rewards. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_campaign_participants accepts 1 parameter: id. Required: id. 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_campaign_participants: 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_campaign_participants 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_campaign_participants 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_campaign_participants. 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_campaign_participants 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