rig_stage_get

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

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/rig-stage-get.md

WHAT IT DOES

What rig_stage_get does on Rokha

AI agents call rig_stage_get 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
`rig_id`	string	Yes	UUID of the saved rig
`wallet_address`	string	Yes	Owner scope

Parameters from the server's own tool schema.

RISK

Why rig_stage_get is rated Low

Retrieves stage configuration without modifying or executing any operations.

From the tool's definition Read a rig's stage configuration back — the template HTML, data_source and title

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rig_stage_get Allowed

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

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

FAQ

Questions about rig_stage_get

What does the rig_stage_get tool do? +

Read a rig's stage configuration back — the template HTML, data_source and title, plus whether it currently validates (a broken stage names what to fix). Use before editing an existing stage so changes are never guess-and-overwrite. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does rig_stage_get accept? +

rig_stage_get accepts 2 parameters: rig_id, wallet_address. Required: rig_id, wallet_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rig_stage_get? +

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

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

Can I rate-limit rig_stage_get? +

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

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

rig_stage_get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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