network_member_report
Requires a JWT. Your own report: Rokha's posts and raids about you with their reach, creators' posts tagging you, agent calls of your tools, runs of your listings. Optional month (YYYY-MM) and agent_id (one of your agents). (network_report, by contrast, is the public size of the whole network.)
This record as markdown: /tools/ai-rokha-rokha/network-member-report.md
What network_member_report does on Rokha
AI agents call network_member_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
month | string | — | YYYY-MM; omit for the last 30 days |
agent_id | string | — |
Parameters from the server's own tool schema.
Why network_member_report is rated Low
Retrieves personal activity and network data about user interactions and agent tool usage with authentication required.
From the tool's definition Your own report: posts, raids, creator posts, agent calls, runs of your listings.
Attacks that exploit this kind of access
The rule that runs network_member_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_member_report, this is the rule to start with:
network_member_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_member_report call is checked against it from then on.
Questions about network_member_report
Requires a JWT. Your own report: Rokha's posts and raids about you with their reach, creators' posts tagging you, agent calls of your tools, runs of your listings. Optional month (YYYY-MM) and agent_id (one of your agents). (network_report, by contrast, is the public size of the whole network.). It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
network_member_report accepts 2 parameters: month, agent_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 network_member_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_member_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_member_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_member_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_member_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