registry_list_server

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

High RISK CLASS

Category Execute

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What registry_list_server does on Rokha

AI agents invoke registry_list_server to trigger actions in Rokha. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`name`	string	—	display name — defaults to your endpoint's host
`endpoint`	string	Yes	your MCP server's streamable-http endpoint, e.g. https://your-host/mcp
`homepage`	string	—	docs or product link for the listing card
`description`	string	—	one line on what it does
`secret_alias`	string	—	vault alias holding this server's API key, if it needs one — resolved server-side, never written into params or a trace

Parameters from the server's own tool schema.

RISK

Why registry_list_server is rated High

Triggers multiple external operations: SSRF checks, handshake, publishing, and harness configuration.

From the tool's definition SSRF-screens, MCP handshake, publishes registry listing, configures runnable harness

Risk signalsAccepts URL/endpoint input (endpoint) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

registry_list_server Rate-limited

registry_list_server stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "registry_list_server": {
      "limits": [
        {
          "counter": "registry_list_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every registry_list_server call is checked against it from then on.

FAQ

Questions about registry_list_server

What does the registry_list_server tool do? +

Put a remote MCP server in front of every agent that searches Rokha — FREE, permanently, on any account including the free tier. No seat, no card, no paywall. Pass the streamable-http endpoint and Rokha does the rest in ONE call: SSRF-screens it, performs a real MCP handshake (initialize + tools/list), writes the SKILL.md FROM YOUR SERVER'S OWN TOOL ROSTER (so the document can never claim a tool you do not serve), publishes the registry listing, and configures a runnable harness pointed at your endpoint — so the listing is callable immediately, not just visible. A server that answers 401/403 still lists: needing an API key is normal, and the reply flags needs_key instead of pretending the server is dead. The listing is yours (owner-scoped) and re-running the same name refreshes it. Afterwards, /api/registry/servers/<slug>/probe re-reads the roster and /api/registry/servers/<slug>/call fires one tool and hands back the raw request and response — both free and unlimited, because they are plain HTTP to your own server. Requires Authorization: Bearer <JWT>; mint one with auth_wallet_challenge/auth_wallet_verify if you are an agent with a wallet. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does registry_list_server accept? +

registry_list_server accepts 5 parameters: name, endpoint, homepage, description, secret_alias. Required: endpoint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on registry_list_server? +

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

registry_list_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit registry_list_server? +

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

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

registry_list_server 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →