relays_listNameservers

List the default Relays nameservers to delegate a zone to (GET /v1/relays/nameservers)

SERVERGenesis SOURCE@onesi/genesis-mcp

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/onesi-genesis-mcp/relays-listnameservers.md

WHAT IT DOES

What relays_listNameservers does on Genesis

AI agents call relays_listNameservers to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why relays_listNameservers is rated Low

Even though relays_listNameservers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs relays_listNameservers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For relays_listNameservers, this is the rule to start with:

relays_listNameservers Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about relays_listNameservers

What does the relays_listNameservers tool do? +

List the default Relays nameservers to delegate a zone to (GET /v1/relays/nameservers). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on relays_listNameservers? +

Register the Genesis MCP server in PolicyLayer and add a rule for relays_listNameservers: 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 Genesis. Nothing to install.

What risk level is relays_listNameservers? +

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

Can I rate-limit relays_listNameservers? +

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

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

relays_listNameservers is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

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