payouts_ledger
The platform's full payout ledger in one read: ad-network carrier payouts (instant — settled the minute revenue lands, with tx signatures), the weekly leaderboard purse (per-round seats, addresses, tx signatures), raid bounties, the revenue side (so 'money moves both ways' is checkable, not claim...
This record as markdown: /tools/ai-rokha-rokha/payouts-ledger.md
What payouts_ledger does on Rokha
AI agents call payouts_ledger 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 payouts_ledger is rated Low
Retrieves financial transaction data and revenue ledgers without modification capability; high severity due to sensitive financial information exposure.
From the tool's definition payout ledger, ad-network payouts, revenue, signatures, public read-only access
Attacks that exploit this kind of access
The rule that runs payouts_ledger 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 payouts_ledger, this is the rule to start with:
payouts_ledger 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 payouts_ledger call is checked against it from then on.
Questions about payouts_ledger
The platform's full payout ledger in one read: ad-network carrier payouts (instant — settled the minute revenue lands, with tx signatures), the weekly leaderboard purse (per-round seats, addresses, tx signatures), raid bounties, the revenue side (so 'money moves both ways' is checkable, not claimed), and the RETENTION metrics — how carrier retention is measured (distinct agents that REPORTED in the trailing 7 days who also reported the 7 days before) and the promoter repeat rate (humans back for a second PAID deal). Addresses and signatures only, never identities. Public, no auth. REST twin: GET https://rokha.ai/api/ledger. 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 payouts_ledger: 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.
payouts_ledger 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 payouts_ledger 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 payouts_ledger. 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.
payouts_ledger 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