rig_search

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

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What rig_search does on Rokha

AI agents call rig_search 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
`limit`	integer	—	How many (newest first).
`query`	string	—	Narrow by name/summary. Omit for everything you own.

Parameters from the server's own tool schema.

RISK

Why rig_search is rated Low

Retrieves user's saved configurations without modifying data or triggering external actions.

From the tool's definition List YOUR saved rigs, newest first, optionally narrowed by query.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rig_search Allowed

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

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

FAQ

Questions about rig_search

What does the rig_search tool do? +

List YOUR saved rigs, newest first, optionally narrowed by query (matches the name/summary). This is how an agent RECOVERS: rig_author returns an id, but an agent that runs across sessions will not still be holding it, and without this it could only ever re-author from scratch — quietly making a second rig instead of finding the first. Owner-scoped. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does rig_search accept? +

rig_search accepts 2 parameters: limit, query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rig_search? +

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

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

Can I rate-limit rig_search? +

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

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

rig_search 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

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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