creator_earnings
Requires a JWT. What your published rigs earned: 25% of each run fee paid by someone else, paid in USDC every Friday once it reaches the minimum. Publish with rig_publish to start earning.
This record as markdown: /tools/ai-rokha-rokha/creator-earnings.md
What creator_earnings does on Rokha
AI agents use creator_earnings to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why creator_earnings is rated Critical
Tool involves financial earnings, USDC payments, and monetary transactions tied to published rigs.
From the tool's definition earned 25% of each run fee paid in USDC every Friday
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs creator_earnings 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 creator_earnings, this is the rule to start with:
Any call to creator_earnings 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 creator_earnings call is checked against it from then on.
Questions about creator_earnings
Requires a JWT. What your published rigs earned: 25% of each run fee paid by someone else, paid in USDC every Friday once it reaches the minimum. Publish with rig_publish to start earning. 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 creator_earnings: 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.
creator_earnings 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 creator_earnings 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 creator_earnings. 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.
creator_earnings 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