neuron_create_ad_request
Create an ad distribution request to send a message to contacts in pool lists matching target demographics. Deducts from wallet upon approval.
This record as markdown: /tools/io-github-conquext-neuron/neuron-create-ad-request.md
What neuron_create_ad_request does on Neuron
AI agents use neuron_create_ad_request to commit financial operations through Neuron, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
budget | number | Yes | Total ad budget in kobo (e.g., 500000 = NGN 5,000) |
message | string | Yes | The ad message content to distribute to matched contacts |
mediaUrl | string | — | Media URL for non-text messages (required when messageType is 'image', 'video', or 'document') |
targetGoal | number | Yes | Target number of successful message deliveries |
messageType | string | — | Message content type: 'text', 'image', 'video', or 'document' (default: 'text') |
targetDemographics | object | Yes | Demographic criteria to match against pool list entries |
Parameters from the server's own tool schema.
Why neuron_create_ad_request is rated Critical
This tool triggers a financial transaction (wallet deduction) as part of its operation. Even though the deduction occurs 'upon approval,' the act of creating the ad request initiates the financial commitment. Financial category takes precedence over all others, and misuse could drain a user's wallet by sending unwanted ad campaigns.
From the tool's definition 'Deducts from wallet upon approval' — directly commits financial obligations by deducting funds from a wallet when the ad request is approved.
Attacks that exploit this kind of access
The rule that runs neuron_create_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_create_ad_request, this is the rule to start with:
Any call to neuron_create_ad_request is blocked until a human approves 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_create_ad_request call is checked against it from then on.
Questions about neuron_create_ad_request
Create an ad distribution request to send a message to contacts in pool lists matching target demographics. Deducts from wallet upon approval. It is categorised as a Financial tool in the Neuron MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
neuron_create_ad_request accepts 6 parameters: budget, message, mediaUrl, targetGoal, messageType, targetDemographics. Required: budget, message, targetGoal, targetDemographics. 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_create_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_create_ad_request is a Financial 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_create_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_create_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_create_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.
Across the catalogue