brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R13.7: Health check hermeticity

Short answer: /healthz endpoints execute lightweight non-allocating probes. A heavy health check can take the service down when it is probed often.

Group: Observability and logging. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R13.7

What it catches

Health check hermeticity: /healthz endpoints execute lightweight non-allocating probes.

Why

A heavy health check can take the service down when it is probed often.

A bad example

app.get('/healthz', async () => await db.query('SELECT count(*) FROM orders'));

A good example

app.get('/healthz', () => ({ ok: true }));

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R13.7 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.