neuron_update_campaign
Update a campaign that is in 'draft' or 'rejected' status. Active or completed campaigns cannot be modified.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-campaign.md
What neuron_update_campaign does on Neuron
AI agents use neuron_update_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 campaign to update |
title | string | — | Updated campaign title |
message | string | — | Updated WhatsApp message template |
deadline | string | — | Updated campaign deadline in ISO 8601 date format |
guidelines | string | — | Updated participant guidelines |
description | string | — | Updated marketplace description |
totalBudget | number | — | Updated total campaign budget in kobo |
rewardPerDelivery | number | — | Updated reward per delivery in kobo (e.g., 5000 = NGN 50) |
requireMutualContact | boolean | — | Updated mutual contact requirement setting |
Parameters from the server's own tool schema.
Why neuron_update_campaign is rated Medium
This tool modifies campaign data (Write category) rather than reading, executing arbitrary operations, or destroying data. The severity is medium because updating campaigns could affect marketing operations and contact communications, but the changes are reversible and limited to non-active campaigns. Confidence is high due to clear action verb 'Update' in both name and description.
From the tool's definition Tool name 'update_campaign' and description 'Update a campaign' indicates modification of existing data. The restriction that only 'draft' or 'rejected' status campaigns can be modified shows the operation is reversible and doesn't permanently destroy data.
Attacks that exploit this kind of access
The rule that runs neuron_update_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_update_campaign, this is the rule to start with:
neuron_update_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_update_campaign call is checked against it from then on.
Questions about neuron_update_campaign
Update a campaign that is in 'draft' or 'rejected' status. Active or completed campaigns cannot be modified. 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_update_campaign accepts 9 parameters: id, title, message, deadline, guidelines, description, totalBudget, rewardPerDelivery, requireMutualContact. 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_update_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_update_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_update_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_update_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_update_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