neuron_pause_campaign
Pause an active campaign to temporarily stop message delivery. Can be resumed later with the resume action.
This record as markdown: /tools/io-github-conquext-neuron/neuron-pause-campaign.md
What neuron_pause_campaign does on Neuron
AI agents use neuron_pause_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 active campaign to pause |
Parameters from the server's own tool schema.
Why neuron_pause_campaign is rated Medium
This tool modifies data (campaign status) reversibly without deleting or destroying it. It is not Execute (doesn't run arbitrary code or commands), not Destructive (the pause is reversible via resume), and not Financial. The severity is medium because pausing a campaign could impact business operations and message delivery to users, but the effect is temporary and reversible, limiting blast radius.
From the tool's definition Tool description states 'Pause an active campaign to temporarily stop message delivery' - this modifies the state of a campaign by changing it from active to paused, which is a reversible operation that can be 'resumed later'.
Attacks that exploit this kind of access
The rule that runs neuron_pause_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_pause_campaign, this is the rule to start with:
neuron_pause_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_pause_campaign call is checked against it from then on.
Questions about neuron_pause_campaign
Pause an active campaign to temporarily stop message delivery. Can be resumed later with the resume action. 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_pause_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_pause_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_pause_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_pause_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_pause_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_pause_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