seeds_recent_posts
THE ROWS BEHIND AN ACCOUNT'S SEED TOTAL. Pass who (a Rokha page handle or an X handle). Each recent post with what it earned, its X-weighted units (replies x5, quotes x5, reposts x1, likes x0.5; seeds = units x10), and why it scored what it did — rule zero (under 2.0 X-weighted earns nothing) or ...
This record as markdown: /tools/ai-rokha-rokha/seeds-recent-posts.md
What seeds_recent_posts does on Rokha
AI agents call seeds_recent_posts 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 |
|---|---|---|---|
who | string | Yes |
Parameters from the server's own tool schema.
Why seeds_recent_posts is rated Low
Tool queries historical post data and financial metrics without modifying or executing external operations.
From the tool's definition retrieves account seed total, recent posts, earnings data; no modifications or deletions
Attacks that exploit this kind of access
The rule that runs seeds_recent_posts 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 seeds_recent_posts, this is the rule to start with:
seeds_recent_posts 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 seeds_recent_posts call is checked against it from then on.
Questions about seeds_recent_posts
THE ROWS BEHIND AN ACCOUNT'S SEED TOTAL. Pass who (a Rokha page handle or an X handle). Each recent post with what it earned, its X-weighted units (replies x5, quotes x5, reposts x1, likes x0.5; seeds = units x10), and why it scored what it did — rule zero (under 2.0 X-weighted earns nothing) or the copied check. Posts from before 2026-10-02 22:00 UTC keep the older units and views they were paid on. Use for 'justify my last posts' or a disputed total, then drill into a row with seeds_explain. An unlinked handle is told its posts are collected and PARKED, crediting retroactively the moment it links. Public, no auth. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
seeds_recent_posts accepts 1 parameter: who. Required: who. 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 seeds_recent_posts: 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.
seeds_recent_posts 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 seeds_recent_posts 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 seeds_recent_posts. 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.
seeds_recent_posts 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