neuron_submit_ad_request
Submit a draft ad request for admin review. The request must be in draft status. After submission, an admin must approve it before it can be funded.
This record as markdown: /tools/io-github-conquext-neuron/neuron-submit-ad-request.md
What neuron_submit_ad_request does on Neuron
AI agents use neuron_submit_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 draft ad request to submit |
Parameters from the server's own tool schema.
Why neuron_submit_ad_request is rated Medium
The tool creates a new ad request record or transitions an existing draft to submitted status. While it involves ads (potentially financial), the tool itself does not commit funds—admin approval is required first, and the description emphasizes the reversible nature of draft submission.
From the tool's definition Tool name 'submit_ad_request' and description states it 'Submit[s] a draft ad request for admin review' and 'after submission, an admin must approve it before it can be funded.' This creates/modifies data (ad request record) in a reversible manner pending…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs neuron_submit_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_submit_ad_request, this is the rule to start with:
neuron_submit_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_submit_ad_request call is checked against it from then on.
Questions about neuron_submit_ad_request
Submit a draft ad request for admin review. The request must be in draft status. After submission, an admin must approve it before it can be funded. 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_submit_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_submit_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_submit_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_submit_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_submit_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_submit_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