network_members
Public. The Rokha Network members in rank order, each with the four signals the rank is built from (last 30 days: promoters = distinct people posting about them, runs of their tools, agent calls of their doors, months on the Network), the score, and why (the lead signal + a one-line summary). Pas...
This record as markdown: /tools/ai-rokha-rokha/network-members.md
What network_members does on Rokha
AI agents call network_members 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 |
|---|---|---|---|
handle | string | — | A member's page or X handle; omit for everyone |
Parameters from the server's own tool schema.
Why network_members is rated Low
Tool queries and returns ranking data without modifying or executing anything.
From the tool's definition retrieves network members, scores, signals; no side effects
Attacks that exploit this kind of access
The rule that runs network_members 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_members, this is the rule to start with:
network_members 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_members call is checked against it from then on.
Questions about network_members
Public. The Rokha Network members in rank order, each with the four signals the rank is built from (last 30 days: promoters = distinct people posting about them, runs of their tools, agent calls of their doors, months on the Network), the score, and why (the lead signal + a one-line summary). Pass handle for one member with the full score arithmetic. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
network_members accepts 1 parameter: handle. 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_members: 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_members 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_members 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_members. 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_members 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