network_pick
Requires a JWT and a linked X account (x_link_start → x_link_verify). Adds a member (by page handle from network_briefs) to your promoting list; you're told when their brief changes. You can't pick yourself.
This record as markdown: /tools/ai-rokha-rokha/network-pick.md
What network_pick does on Rokha
AI agents call network_pick 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 | Yes |
Parameters from the server's own tool schema.
Why network_pick is rated Low
Even though network_pick only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs network_pick 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_pick, this is the rule to start with:
network_pick 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_pick call is checked against it from then on.
Questions about network_pick
Requires a JWT and a linked X account (x_link_start → x_link_verify). Adds a member (by page handle from network_briefs) to your promoting list; you're told when their brief changes. You can't pick yourself. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
network_pick accepts 1 parameter: handle. Required: 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_pick: 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_pick 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_pick 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_pick. 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_pick 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