relays_listCertificates
List certificates with filters, stats and pagination (GET /v1/relays/certificates)
This record as markdown: /tools/onesi-genesis-mcp/relays-listcertificates.md
What relays_listCertificates does on Genesis
AI agents call relays_listCertificates 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | |
sort | string | — | |
limit | integer | — | |
order | string | — | |
search | string | — | Substring of the common name, or an exact SAN |
status | string | — | |
cert_type | string | — | |
domain_id | integer | — | |
is_custom | string | — | |
auto_renew | string | — | |
expiring_within_days | integer | — | Issued certificates expiring within this many days |
Parameters from the server's own tool schema.
Why relays_listCertificates is rated Low
Even though relays_listCertificates 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 signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs relays_listCertificates 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_listCertificates, this is the rule to start with:
relays_listCertificates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every relays_listCertificates call is checked against it from then on.
Questions about relays_listCertificates
List certificates with filters, stats and pagination (GET /v1/relays/certificates). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
relays_listCertificates accepts 11 parameters: page, sort, limit, order, search, status, cert_type, domain_id, is_custom, auto_renew, expiring_within_days. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for relays_listCertificates: 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.
relays_listCertificates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the relays_listCertificates 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.
Set action: deny in the PolicyLayer policy for relays_listCertificates. 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.
relays_listCertificates 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.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue