R14.8: Role-based access control

Short answer: Enforce authorization check at controller/handler boundary. A check that lives only in the UI is skipped by anyone who calls the API.

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

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R14.8

What it catches

Role-based access control: enforce authorization check at controller/handler boundary.

Why

A check that lives only in the UI is skipped by anyone who calls the API.

A bad example

app.delete('/users/:id', removeUser);

A good example

app.delete('/users/:id', requireRole('admin'), removeUser);

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

R14.1 Session token entropy
R14.2 Password hash modern algorithms
R14.3 Token expiration bounding
R14.4 CSRF token validation
Every rule