adnet_stats
The ad network's live state — settled revenue all-time, any pool parked waiting for its first carrier (house 50%), the number of publishers, the top reporters (handles or short addresses), the last settled round, and whether payouts are live. Public.
This record as markdown: /tools/ai-rokha-rokha/adnet-stats.md
What adnet_stats does on Rokha
AI agents call adnet_stats to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adnet_stats is rated Low
Tool queries ad network statistics without modifying data or executing commands.
From the tool's definition retrieves live state, settled revenue, publishers, reporters, last settled round, payouts status
Attacks that exploit this kind of access
The rule that runs adnet_stats 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_stats, this is the rule to start with:
adnet_stats 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 Rokha, apply this rule, and every adnet_stats call is checked against it from then on.
Questions about adnet_stats
The ad network's live state — settled revenue all-time, any pool parked waiting for its first carrier (house 50%), the number of publishers, the top reporters (handles or short addresses), the last settled round, and whether payouts are live. Public. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
Register the Rokha MCP server in PolicyLayer and add a rule for adnet_stats: 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_stats 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 adnet_stats 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_stats. 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_stats 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