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.8: Exception traceback containment

Short answer: Sanitize public error responses to avoid leaking paths. A stack trace in a reply shows file paths and internals to the caller.

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

What it catches

Exception traceback containment: sanitize public error responses to avoid leaking paths.

Why

A stack trace in a reply shows file paths and internals to the caller.

A bad example

res.status(500).send(err.stack);

A good example

log.error(err);
res.status(500).json({ error: { code: 'internal' } });

How it is checked

How to silence it

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