neuron_update_ad_request
Update a draft or rejected ad request. Only draft and rejected ad requests can be edited. Rejected requests revert to draft on update.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-ad-request.md
What neuron_update_ad_request does on Neuron
AI agents use neuron_update_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 |
|---|---|---|---|
budget | number | — | Updated budget in kobo |
message | string | — | Updated ad message content |
mediaUrl | string | — | Updated media URL (set to null to clear) |
targetGoal | number | — | Updated target number of deliveries |
targetType | string | — | Target type: 'contacts' or 'groups' |
adRequestId | string | Yes | Unique identifier (UUID) of the ad request to update |
messageType | string | — | Updated message type: 'text', 'image', 'video', or 'document' |
targetingMode | string | — | Targeting mode: 'auto' for system matching or 'manual' for hand-picked pool entries |
targetDemographics | object | — | Updated demographic targeting criteria |
selectedPoolEntryIds | array | — | Pool entry UUIDs for manual contact targeting |
selectedGroupPoolEntryIds | array | — | Group pool entry UUIDs for manual group targeting |
Parameters from the server's own tool schema.
Why neuron_update_ad_request is rated Medium
This tool modifies existing ad request records by allowing updates to draft or rejected requests. While reversible (rejected requests revert to draft status, implying prior states can be recovered), it creates or modifies business records in the ad campaign system. The impact is limited to ad request objects rather than destructive deletion or financial transactions, placing it in the Write category.
From the tool's definition Tool description states it performs 'Update a draft or rejected ad request' and allows editing of requests that 'revert to draft on update', which are clearly data modification operations.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs neuron_update_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_update_ad_request, this is the rule to start with:
neuron_update_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_update_ad_request call is checked against it from then on.
Questions about neuron_update_ad_request
Update a draft or rejected ad request. Only draft and rejected ad requests can be edited. Rejected requests revert to draft on update. 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_ad_request accepts 11 parameters: budget, message, mediaUrl, targetGoal, targetType, adRequestId, messageType, targetingMode, targetDemographics, selectedPoolEntryIds, selectedGroupPoolEntryIds. 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_update_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_update_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_update_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_update_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_update_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