justify_seeds
The per-post arithmetic behind any Tailwind board seat: give it an X or page handle and get how that account's seeds are earned this round. Every qualifying post since the last payout is scored the way X's open-source ranker scores (xai-org/x-algorithm): reply 5 · quote 5 · repost 1 · like 0.5, a...
This record as markdown: /tools/ai-rokha-rokha/justify-seeds.md
What justify_seeds does on Rokha
AI agents call justify_seeds 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | The X handle or page handle whose seat to justify, e.g. '@somebody'. |
Parameters from the server's own tool schema.
Why justify_seeds is rated Low
Tool retrieves and calculates seed earnings data without modifying state or triggering external actions.
From the tool's definition give it an X or page handle and get how that account's seeds are earned
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs justify_seeds 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 justify_seeds, this is the rule to start with:
justify_seeds 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 justify_seeds call is checked against it from then on.
Questions about justify_seeds
The per-post arithmetic behind any Tailwind board seat: give it an X or page handle and get how that account's seeds are earned this round. Every qualifying post since the last payout is scored the way X's open-source ranker scores (xai-org/x-algorithm): reply 5 · quote 5 · repost 1 · like 0.5, a straight weighted sum ×10 seeds with no per-post cap, then a DAY DECAY per author per UTC day: the best 3 posts earn in full, the 4th earns min(seeds, 100) × 0.5, the 5th × 0.25, the 6th × 0.125, the 7th on earns 0 — each post line carries day_rank, rank_mult and raw_seeds (a proven word-for-word copy earns ×0; posts before 2026-10-02 22:00 UTC keep the older damped, capped, best-5 math). Counts only: no model verdict and no profile bonus weight the score (removed 2026-09-24). Returns the total, the per-post breakdown, and a human-readable explanation — the SAME numbers the weekly purse pays from. Public, no auth. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
justify_seeds accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for justify_seeds: 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.
justify_seeds 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 justify_seeds 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 justify_seeds. 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.
justify_seeds 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