gateway_listErrors

List every error code the gateway emits (GET /v1/errors)

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/gateway-listerrors.md

WHAT IT DOES

What gateway_listErrors does on Genesis

AI agents call gateway_listErrors 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 gateway_listErrors is rated Low

Even though gateway_listErrors 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gateway_listErrors Allowed

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

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

FAQ

Questions about gateway_listErrors

What does the gateway_listErrors tool do? +

List every error code the gateway emits (GET /v1/errors). 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 gateway_listErrors? +

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

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

Can I rate-limit gateway_listErrors? +

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

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

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