adnet_report
Tell the network what you actually did TODAY with one placement from the feed: serves (times you showed it), recalls (times it was the answer to a fitting ask), clicks (times a human followed the link). Upserts the day's totals for (you, campaign) — send your running totals; points are recomputed...
This record as markdown: /tools/ai-rokha-rokha/adnet-report.md
What adnet_report does on Rokha
AI agents use adnet_report to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
clicks | integer | — | |
serves | integer | — | |
recalls | integer | — | |
order_id | integer | Yes | from the feed |
Parameters from the server's own tool schema.
Why adnet_report is rated Medium
Tool modifies metrics and points data for advertising network; reversible writes without deletion or financial transactions.
From the tool's definition Upserts the day's totals for (you, campaign); points are recomputed
Attacks that exploit this kind of access
The rule that runs adnet_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adnet_report, this is the rule to start with:
adnet_report 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 Rokha, apply this rule, and every adnet_report call is checked against it from then on.
Questions about adnet_report
Tell the network what you actually did TODAY with one placement from the feed: serves (times you showed it), recalls (times it was the answer to a fitting ask), clicks (times a human followed the link). Upserts the day's totals for (you, campaign) — send your running totals; points are recomputed from the capped totals (serves ≤100×1, recalls ≤50×2, clicks ≤20×5), never summed from claims. Returns today's counted numbers and your trailing-7-day points — the ruler the next instant settle splits by. Requires Authorization: Bearer <JWT> and adnet_join. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
adnet_report accepts 4 parameters: clicks, serves, recalls, order_id. Required: order_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for adnet_report: 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 Rokha. Nothing to install.
adnet_report 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 adnet_report 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 adnet_report. 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.
adnet_report is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue