search_harnesses

Search harnesses by query string within a wallet

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

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What search_harnesses does on Rokha

AI agents call search_harnesses 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
`query`	string	Yes	Search query
`harness_type`	string	—	Filter by harness type (optional)
`wallet_address`	string	—	Wallet address to search within

Parameters from the server's own tool schema.

RISK

Why search_harnesses is rated Low

Tool queries and retrieves harness data without modifying or executing operations.

From the tool's definition Search harnesses by query string within a wallet

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_harnesses Allowed

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

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

FAQ

Questions about search_harnesses

What does the search_harnesses tool do? +

Search harnesses by query string within a wallet. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does search_harnesses accept? +

search_harnesses accepts 3 parameters: query, harness_type, wallet_address. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_harnesses? +

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

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

Can I rate-limit search_harnesses? +

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

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

search_harnesses 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 →