network_pot
Public. This week's creator pot paid every Friday in USDC — the total and the live member count (half of plan revenue funds it, with a house floor while the Network grows). Next for promoters: network_briefs, then network_pick.
This record as markdown: /tools/ai-rokha-rokha/network-pot.md
What network_pot does on Rokha
AI agents call network_pot 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_pot is rated Low
Tool reads and returns financial pot data without moving money or committing obligations.
From the tool's definition total and the live member count
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs network_pot 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_pot, this is the rule to start with:
network_pot 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_pot call is checked against it from then on.
Questions about network_pot
Public. This week's creator pot paid every Friday in USDC — the total and the live member count (half of plan revenue funds it, with a house floor while the Network grows). Next for promoters: network_briefs, then network_pick. 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_pot: 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_pot 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_pot 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_pot. 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_pot 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