# Risk Assessment Boundaries — Changelog
[ 
Changelog
](/changelog) June 9, 2026 [ Risk Management ](/changelog?tag=Risk%20Management) 
# Risk Assessment Boundaries

Group risk assessment nodes into named, nestable boundaries so large Mermaid diagrams stay readable as your system map grows. 

[Risk assessment diagrams](/docs/product/risk-management) get messy once a team maps more than a handful of nodes. Everything lives on one flat canvas, so scope boundaries only exist in someone’s head.
-risk-assessment
Boundaries fix that. Create a boundary within a risk assessment scope, then assign nodes to it. The Mermaid diagram renders each boundary as its own labeled subgraph, so you can see at a glance which nodes belong to which part of the system. Boundaries can nest inside each other too, for teams that split assessments by business unit and then by system.

It’s available in the console, the CLI (prb risk-assessment boundary), and through [MCP tools](/docs/developers/api/mcp/tools/catalog/risk-assessments).