network_briefs
Public. Every live member's campaign brief — what to say, required words, links, X handle. Promote a member by posting from your linked X account and tagging them — the post qualifies for the weekly Tailwind payout and scores on its own engagement (no tag boosts). Next: network_pick (JWT) to foll...
This record as markdown: /tools/ai-rokha-rokha/network-briefs.md
What network_briefs does on Rokha
AI agents call network_briefs 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_briefs is rated Low
Tool retrieves public campaign briefs and promotional information without modifying data or executing actions.
From the tool's definition Every live member's campaign brief — what to say, required words, links, X handle. Public.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs network_briefs 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_briefs, this is the rule to start with:
network_briefs 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_briefs call is checked against it from then on.
Questions about network_briefs
Public. Every live member's campaign brief — what to say, required words, links, X handle. Promote a member by posting from your linked X account and tagging them — the post qualifies for the weekly Tailwind payout and scores on its own engagement (no tag boosts). Next: network_pick (JWT) to follow a member, x_link_start to link X, carry_brief for the full earn rules. 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_briefs: 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_briefs 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_briefs 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_briefs. 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_briefs 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