R10.3: Rate-limit header handling

Short answer: Parse 429 Retry-After and respect backoff deadlines. Ignoring Retry-After keeps you rate limited for longer.

Group: API and network robustness. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R10.3

What it catches

Rate-limit header handling: parse 429 Retry-After and respect backoff deadlines.

Why

Ignoring Retry-After keeps you rate limited for longer.

A bad example

if (res.status === 429) return call();

A good example

if (res.status === 429) await sleep(retryAfterMs(res));

How it is checked

Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

A person can silence one finding with brevio-core: ignore R10.3 -- 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.

R10.4 Structured error envelope
R10.5 Response size bounding
R10.6 Content-Type negotiation
R10.7 No unauthenticated admin endpoints
Every rule