gateway_list

List the servers registered behind your Rokha gateway (slug, URL, authenticating alias) plus the single gateway_url an MCP client connects to. Requires login.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What gateway_list does on Rokha

AI agents call gateway_list 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.

RISK

Why gateway_list is rated Low

Queries registry metadata about available servers; no side effects but reveals infrastructure requiring authentication.

From the tool's definition list the servers registered, requires login, no modification

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gateway_list Allowed

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

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

FAQ

Questions about gateway_list

What does the gateway_list tool do? +

List the servers registered behind your Rokha gateway (slug, URL, authenticating alias) plus the single gateway_url an MCP client connects to. Requires login. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gateway_list? +

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

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

Can I rate-limit gateway_list? +

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

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

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