neuron_submit_campaign
Submit a draft campaign for admin review and approval. The campaign must be in 'draft' status.
This record as markdown: /tools/io-github-conquext-neuron/neuron-submit-campaign.md
What neuron_submit_campaign does on Neuron
AI agents use neuron_submit_campaign to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the draft campaign to submit for review |
Parameters from the server's own tool schema.
Why neuron_submit_campaign is rated Medium
This tool changes campaign state and initiates an approval workflow, which is a reversible modification of data. It does not execute arbitrary code, delete data, or move money. The 'submit' action transitions the campaign status, making it a Write operation.
From the tool's definition Tool performs 'Submit a draft campaign for admin review and approval' - creates or modifies the state of a campaign resource from 'draft' to a submitted/pending status, triggering a workflow change without permanent destruction.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs neuron_submit_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_submit_campaign, this is the rule to start with:
neuron_submit_campaign stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_submit_campaign call is checked against it from then on.
Questions about neuron_submit_campaign
Submit a draft campaign for admin review and approval. The campaign must be in 'draft' status. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_submit_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_submit_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_submit_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the neuron_submit_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_submit_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_submit_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