neuron_resume_ad_request
Resume a paused ad request campaign. Distribution resumes from where it left off. Only paused ad requests can be resumed.
This record as markdown: /tools/io-github-conquext-neuron/neuron-resume-ad-request.md
What neuron_resume_ad_request does on Neuron
AI agents use neuron_resume_ad_request 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 |
|---|---|---|---|
adRequestId | string | Yes | Unique identifier (UUID) of the paused ad request to resume |
Parameters from the server's own tool schema.
Why neuron_resume_ad_request is rated Medium
Resuming a paused campaign modifies its state (paused → active) and restarts message distribution. This is a reversible state change (it can be paused again), so it falls under Write rather than Execute or Destructive. Misuse could trigger unintended mass messaging to contacts, giving it medium severity.
From the tool's definition Resume a paused ad request campaign. Distribution resumes from where it left off.
Attacks that exploit this kind of access
The rule that runs neuron_resume_ad_request 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_resume_ad_request, this is the rule to start with:
neuron_resume_ad_request 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_resume_ad_request call is checked against it from then on.
Questions about neuron_resume_ad_request
Resume a paused ad request campaign. Distribution resumes from where it left off. Only paused ad requests can be resumed. 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_resume_ad_request accepts 1 parameter: adRequestId. Required: adRequestId. 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_resume_ad_request: 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_resume_ad_request 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_resume_ad_request 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_resume_ad_request. 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_resume_ad_request 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