neuron_delete_campaign
Permanently delete a campaign that is in 'draft' status. Active or funded campaigns cannot be deleted.
This record as markdown: /tools/io-github-conquext-neuron/neuron-delete-campaign.md
What neuron_delete_campaign does on Neuron
AI agents call neuron_delete_campaign to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the draft campaign to delete |
Parameters from the server's own tool schema.
Why neuron_delete_campaign is rated Critical
This tool performs an irreversible deletion of campaign data. Although the scope is limited to draft campaigns (reducing blast radius compared to active/funded campaigns), the permanent nature of the deletion and inability to undo the action classifies it as Destructive rather than Write.
From the tool's definition 'Permanently delete a campaign' - the tool irreversibly removes campaign data. The description explicitly states 'Permanently delete' which indicates an unrecoverable deletion action.
Attacks that exploit this kind of access
The rule that runs neuron_delete_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_delete_campaign, this is the rule to start with:
neuron_delete_campaign is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_delete_campaign call is checked against it from then on.
Questions about neuron_delete_campaign
Permanently delete a campaign that is in 'draft' status. Active or funded campaigns cannot be deleted. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_delete_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_delete_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_delete_campaign is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neuron_delete_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_delete_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_delete_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.
Across the catalogue