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

R10.5: Response size bounding

Short answer: Clamp response body reads to avoid unbounded buffer allocation. Reading a response without a cap lets one big reply use all the memory.

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.5

What it catches

Response size bounding: clamp response body reads to avoid unbounded buffer allocation.

Why

Reading a response without a cap lets one big reply use all the memory.

A bad example

const text = await res.text();

A good example

const text = await readCapped(res, 1_000_000);

How it is checked

How to silence it

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