network_referral
Requires a JWT. Your referral link (rokha.ai/network?ref=<your handle>) and its status. Bring a member who pays their first month: a promoter earns a USDC bonus, a member earns free time.
This record as markdown: /tools/ai-rokha-rokha/network-referral.md
What network_referral does on Rokha
AI agents use network_referral to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why network_referral is rated Critical
Tool involves financial rewards in USDC, constituting financial obligations and commitments.
From the tool's definition earns a USDC bonus, member earns free time
Attacks that exploit this kind of access
The rule that runs network_referral 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_referral, this is the rule to start with:
Any call to network_referral is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every network_referral call is checked against it from then on.
Questions about network_referral
Requires a JWT. Your referral link (rokha.ai/network?ref=<your handle>) and its status. Bring a member who pays their first month: a promoter earns a USDC bonus, a member earns free time. It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Rokha MCP server in PolicyLayer and add a rule for network_referral: 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_referral is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the network_referral 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_referral. 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_referral 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.
Across the catalogue