Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Verify HMAC against raw request text before JSON parse. Parsing the JSON first changes the bytes, so the signature no longer matches and a forged call can pass.
Group: Security and tenancy. Status: stable. Generated from the rule definitions; do not edit by hand.
Playground: https://brevio.pro/tools/agent-guard-playground?rule=R2.4
Raw-body webhook verification: verify HMAC against raw request text before JSON parse.
Parsing the JSON first changes the bytes, so the signature no longer matches and a forged call can pass.
const body = await req.json();
verifySignature(body, sig);
const raw = await req.text();
verifySignature(raw, sig);
const body = JSON.parse(raw);
dev_rules.scan_added_lines); brevio-core scan does not run it.dev_rules.slice_micro_rules).A person can silence one finding with brevio-core: ignore R2.4 -- 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.
A scan reads only the lines you add, so a line that was already in the file is not flagged.
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.