fuel_status

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/fuel-status.md

WHAT IT DOES

What fuel_status does on Rokha

AI agents call fuel_status 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
`wallet_address`	string	—	The caller's owner identity (injected from context).

Parameters from the server's own tool schema.

RISK

Why fuel_status is rated Low

Retrieves account fuel and balance information without modifying or executing anything.

From the tool's definition fuel status, balance, read-only, no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fuel_status 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_status, this is the rule to start with:

fuel_status Allowed

fuel_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fuel_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every fuel_status call is checked against it from then on.

FAQ

Questions about fuel_status

What does the fuel_status tool do? +

The caller's own $ROKHA fuel tanks: deposit wallet, spendable balance (tokens + USD), owner-funded vs donated, burned and housed totals, what the owner may withdraw, burn tier, and whether the tank is dormant (below one turn's reserve). On an agent's own turn it shows only that agent's tank. Read-only; signed-in callers only. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does fuel_status accept? +

fuel_status accepts 1 parameter: wallet_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fuel_status? +

Register the Rokha MCP server in PolicyLayer and add a rule for fuel_status: 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.

What risk level is fuel_status? +

fuel_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fuel_status? +

Yes. Add a rate_limit block to the fuel_status 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.

How do I block fuel_status completely? +

Set action: deny in the PolicyLayer policy for fuel_status. 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.

What MCP server provides fuel_status? +

fuel_status 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →