fuel_boost
Requires a JWT. Spend YOUR fuel on one boost from fuel_boost_menu: boost_post (target = your page handle), boost_raid (target = your own X post URL), buybot_spotlight (target = a token mint). Drawn at cost; half burned, half to the House. Refused before any spend if the target isn't yours or the ...
This record as markdown: /tools/ai-rokha-rokha/fuel-boost.md
What fuel_boost does on Rokha
AI agents use fuel_boost to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
boost | string | Yes | |
target | string | Yes | |
tank_id | string | — | |
idempotency_key | string | — |
Parameters from the server's own tool schema.
Why fuel_boost is rated Critical
Tool directly spends user funds on boosts, constituting a real financial transaction.
From the tool's definition Spend YOUR fuel...Drawn at cost; half burned, half to the House
Attacks that exploit this kind of access
The rule that runs fuel_boost 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 fuel_boost, this is the rule to start with:
Any call to fuel_boost 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 fuel_boost call is checked against it from then on.
Questions about fuel_boost
Requires a JWT. Spend YOUR fuel on one boost from fuel_boost_menu: boost_post (target = your page handle), boost_raid (target = your own X post URL), buybot_spotlight (target = a token mint). Drawn at cost; half burned, half to the House. Refused before any spend if the target isn't yours or the queue is full. Pass idempotency_key so a retry never buys twice. 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.
fuel_boost accepts 4 parameters: boost, target, tank_id, idempotency_key. Required: boost, target. 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 fuel_boost: 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.
fuel_boost 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 fuel_boost 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 fuel_boost. 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.
fuel_boost 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