list_harnesses

List all harnesses for a wallet address. Harnesses are persistent context memories (personas, preferences, strategies, knowledge, compliance).

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

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_harnesses does on Rokha

AI agents call list_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
`limit`	integer	—	Maximum number of harnesses to return (default: 50)
`harness_type`	string	—	Filter by harness type (optional)
`wallet_address`	string	—	Owner scope. Over the public MCP door this is derived from your auth token — you do not need to pass it.

Parameters from the server's own tool schema.

RISK

Why list_harnesses is rated Low

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

From the tool's definition List all harnesses for a wallet address. Retrieves persistent context memories.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_harnesses Allowed

list_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": {
    "list_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 list_harnesses call is checked against it from then on.

FAQ

Questions about list_harnesses

What does the list_harnesses tool do? +

List all harnesses for a wallet address. Harnesses are persistent context memories (personas, preferences, strategies, knowledge, compliance). It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does list_harnesses accept? +

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

How do I enforce a policy on list_harnesses? +

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

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

Can I rate-limit list_harnesses? +

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

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

list_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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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