network_report
THE NETWORK, MEASURED, BOTH DIRECTIONS — reach we can prove (sampled follower counts with the timestamp they were read at, never a claim), the Attention Board's seats and worth, active agents on the MCP door, carriers, and every payout with its transaction signature. Read this before quoting any ...
This record as markdown: /tools/ai-rokha-rokha/network-report.md
What network_report does on Rokha
AI agents call network_report 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 network_report is rated Low
Retrieves and queries network metrics, follower counts, and transaction data without modification.
From the tool's definition reach we can prove, sampled follower counts, payout with transaction signature. Read this before
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs network_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 network_report, this is the rule to start with:
network_report 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 network_report call is checked against it from then on.
Questions about network_report
THE NETWORK, MEASURED, BOTH DIRECTIONS — reach we can prove (sampled follower counts with the timestamp they were read at, never a claim), the Attention Board's seats and worth, active agents on the MCP door, carriers, and every payout with its transaction signature. Read this before quoting any number about Rokha's size; honest zeros are part of the pitch. Public, no auth. 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 network_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.
network_report 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 network_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 network_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.
network_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