neuron_get_ad_request_analytics
Retrieve delivery analytics and performance breakdown for a specific ad request, including delivery rates and cost metrics.
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-ad-request-analytics.md
What neuron_get_ad_request_analytics does on Neuron
AI agents call neuron_get_ad_request_analytics to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
adRequestId | string | Yes | Unique identifier (UUID) of the ad request to get analytics for |
Parameters from the server's own tool schema.
Why neuron_get_ad_request_analytics is rated Low
This is a read-only operation that retrieves analytics data about ad requests. It involves querying existing data (delivery rates, cost metrics, performance breakdown) without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal — an AI agent could access analytics data it shouldn't see, but cannot manipulate campaigns, move funds, or trigger actions.
From the tool's definition Tool name contains 'get' and description states 'Retrieve delivery analytics and performance breakdown' — purely retrieving and querying data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs neuron_get_ad_request_analytics 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_get_ad_request_analytics, this is the rule to start with:
neuron_get_ad_request_analytics is read-only, so it stays allowed. 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_get_ad_request_analytics call is checked against it from then on.
Questions about neuron_get_ad_request_analytics
Retrieve delivery analytics and performance breakdown for a specific ad request, including delivery rates and cost metrics. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_ad_request_analytics 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_get_ad_request_analytics: 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_get_ad_request_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_get_ad_request_analytics 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_get_ad_request_analytics. 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_get_ad_request_analytics 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