fuel_menu

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What fuel_menu does on Rokha

AI agents call fuel_menu 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.

RISK

Why fuel_menu is rated Low

Tool retrieves pricing and product information without modification or side effects.

From the tool's definition Read-only, fuel tank menu query, displays prices and burn tier information.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

fuel_menu Allowed

fuel_menu 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_menu": {}
  }
}

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_menu call is checked against it from then on.

FAQ

Questions about fuel_menu

What does the fuel_menu tool do? +

What a $ROKHA fuel tank can buy besides inference: each item's id, label, USD price and the burn tier it needs. Fuel runs at cost — half of every $ROKHA spent is burned, half goes to House. Read-only. REST twin: https://rokha.ai/api/fuel/menu. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fuel_menu? +

Register the Rokha MCP server in PolicyLayer and add a rule for fuel_menu: 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_menu? +

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

Can I rate-limit fuel_menu? +

Yes. Add a rate_limit block to the fuel_menu 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_menu completely? +

Set action: deny in the PolicyLayer policy for fuel_menu. 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_menu? +

fuel_menu 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

The MCP Attack Database →

Guides

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