boosts_explain
EVERY MULTIPLIER, AND WHICH ARE LIVE ON AN ACCOUNT. Bare = the full menu. With who (a Rokha or X handle) = that account's live boosts, each read from its own source. NO TAG BOOSTS for posts made since 2026-10-02 22:00 UTC (a carry x1.25-x1.50 shows only on older posts, stamped once at collection)...
This record as markdown: /tools/ai-rokha-rokha/boosts-explain.md
What boosts_explain does on Rokha
AI agents call boosts_explain 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 | — |
Parameters from the server's own tool schema.
Why boosts_explain is rated Low
Retrieves boosts and multipliers from accounts; queries data without side effects or authentication.
From the tool's definition read from its own source, no auth, returns multiplier information
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs boosts_explain 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 boosts_explain, this is the rule to start with:
boosts_explain 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 boosts_explain call is checked against it from then on.
Questions about boosts_explain
EVERY MULTIPLIER, AND WHICH ARE LIVE ON AN ACCOUNT. Bare = the full menu. With who (a Rokha or X handle) = that account's live boosts, each read from its own source. NO TAG BOOSTS for posts made since 2026-10-02 22:00 UTC (a carry x1.25-x1.50 shows only on older posts, stamped once at collection). COPIED x0: a word-for-word copy of an earlier post earns nothing, proven by a duplicate check. And RULE ZERO, the floor that beats them all. Public, no auth. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
boosts_explain accepts 1 parameter: 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 boosts_explain: 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.
boosts_explain 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 boosts_explain 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 boosts_explain. 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.
boosts_explain 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