neuron_get_campaign
Retrieve detailed information about a specific campaign including its status, budget, participants, and delivery metrics.
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-campaign.md
What neuron_get_campaign does on Neuron
AI agents call neuron_get_campaign 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 |
Parameters from the server's own tool schema.
Why neuron_get_campaign is rated Low
This tool retrieves campaign data (status, budget, participants, delivery metrics) without creating, modifying, or deleting any information. It is a simple query operation with no side effects, fitting the Read category. The severity is low as it only accesses campaign metadata without enabling any damaging actions. High confidence due to clear retrieval-only semantics in both name and description.
From the tool's definition Tool name includes 'get' and description states 'Retrieve detailed information about a specific campaign' with no modification or deletion capability mentioned.
Attacks that exploit this kind of access
The rule that runs neuron_get_campaign 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_get_campaign, this is the rule to start with:
neuron_get_campaign 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_get_campaign call is checked against it from then on.
Questions about neuron_get_campaign
Retrieve detailed information about a specific campaign including its status, budget, participants, and delivery metrics. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_campaign 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_get_campaign: 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_get_campaign 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_get_campaign 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_get_campaign. 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_get_campaign 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