neuron_my_participations
Retrieve all campaigns the current organization has joined as a participant, including earnings and delivery stats.
This record as markdown: /tools/io-github-conquext-neuron/neuron-my-participations.md
What neuron_my_participations does on Neuron
AI agents call neuron_my_participations 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default: 1) |
limit | integer | — | Number of participations per page (default: 20) |
Parameters from the server's own tool schema.
Why neuron_my_participations is rated Low
This tool performs a read-only query operation that retrieves existing data about campaign participations, earnings, and delivery statistics. There are no side effects, no data modification, creation, or deletion. The blast radius is minimal since it only exposes information already accessible to the authenticated organization. Classification as Read is appropriate.
From the tool's definition Tool retrieves campaign participation data with 'earnings and delivery stats' for the current organization. Uses retrieval verbs: 'Retrieve all campaigns'.
Attacks that exploit this kind of access
The rule that runs neuron_my_participations 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_my_participations, this is the rule to start with:
neuron_my_participations 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_my_participations call is checked against it from then on.
Questions about neuron_my_participations
Retrieve all campaigns the current organization has joined as a participant, including earnings and delivery stats. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_my_participations accepts 2 parameters: page, limit. 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_my_participations: 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_my_participations 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_my_participations 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_my_participations. 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_my_participations 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