Skip to content

Writes outside the workspace

A recognized file write targets a location outside the workspace roots used for the session.

An unintended write can change another project, modify shared configuration, or place sensitive data where it does not belong.

An agent editing an application writes a configuration file into an unrelated project directory.

This is a fictional example, not an event from a customer.

The rule evaluates recognized write targets against the session starting and current directories, their recognized Git checkouts, and configured workspace roots when that context is available.

Rule IDEvent categoryTierBase severity
RULE_CWD_BOUNDARY_WRITEcwd_boundaryCommunityMEDIUM

Base severity is the rule default. A finding involving content saved for later execution may have a lower severity. Your loaded rule version and event details determine the finding you see.

Check the target and task authorization. Add legitimate roots through configuration when needed, while keeping the allowed scope appropriate to the work.

An authorized shared configuration update or a legitimate additional project omitted from workspace_roots can trigger it.

Calls without working-directory metadata are skipped. Unsupported write syntax, relative or unresolved variable paths, and indirect filesystem effects can be missed.

This rule concerns writes, not ordinary reads outside the workspace. Detection is based on captured targets and available context, and does not replace filesystem access controls.

A finding describes a pattern in captured activity. Review the original call, its result, and the task context before concluding that harm occurred. Absence of a finding does not establish that an operation is safe.

Browse this category. Find a rule by ID.