{"version":"2.1.257","anchor":"artifact-database-writeread-tool-respects-the-read-block-se","canonical_anchor":"artifact-database-writeread-tool-respects-the-read-block-se","heading":"Artifact database write\/read tool respects the read-block setting","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-database-writeread-tool-respects-the-read-block-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact database write\/read tool respects the read-block setting\n\nArtifact database reads and writes now honor the setting that confines file access to your working directories.\n\nThe artifact database tool's file-backed reads and writes (`db_op` paths, `file_path` resolution) now route through the same working-directory checks as other file access, so `blockReadsOutsideWorkingDirectories` also constrains which local files can be used as data sources or destinations for artifact database operations. The read\/write sub-tool is only enabled when its gating check returns true.\n\n- Flag `tengu_umber_lattice`: Off in both readings (read for one account on one subscription tier against v2.1.257; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Names: `blockReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}