relays_getMonitorSloBurnRates

Calculate error budget burn rates for enabled SLOs (GET /v1/relays/monitors/slos/burn-rate)

SERVERGenesis SOURCE@onesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/relays-getmonitorsloburnrates.md

WHAT IT DOES

What relays_getMonitorSloBurnRates does on Genesis

AI agents call relays_getMonitorSloBurnRates 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
`slo_id`	string	—
`monitor_id`	string	—

Parameters from the server's own tool schema.

RISK

Why relays_getMonitorSloBurnRates is rated Low

Even though relays_getMonitorSloBurnRates 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_getMonitorSloBurnRates 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_getMonitorSloBurnRates, this is the rule to start with:

relays_getMonitorSloBurnRates Allowed

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

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

FAQ

Questions about relays_getMonitorSloBurnRates

What does the relays_getMonitorSloBurnRates tool do? +

Calculate error budget burn rates for enabled SLOs (GET /v1/relays/monitors/slos/burn-rate). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

What parameters does relays_getMonitorSloBurnRates accept? +

relays_getMonitorSloBurnRates accepts 2 parameters: slo_id, monitor_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on relays_getMonitorSloBurnRates? +

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

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

Can I rate-limit relays_getMonitorSloBurnRates? +

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

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

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