Unverified50% confidenceFactExact time
The trigger condition for blockWritesOutsideWorkingDirectories is that the target path falls outside the working directory; in that case the tool call is rejected rather than written first and then reported as an error.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/3/2026
First Seen
Valid until: 2/1/2027
Sources
Related Entities
Related Claims
Unverifiedv2.1.314 adds the configuration permissions.blockWritesOutsideWorkingDirectories; once enabled, the three file-writing tools Write, Edit, and NotebookEdit reject paths outside the working directory under any permission mode.76% similarUnverifiedIn auto mode, a one-time prompt will appear before reading files outside the working directory for the first time, and users can block such reads via permissions.blockReadsOutsideWorkingDirectories.70% similarUnverifiedThe file management Agent example in the article omits the actual execution of tool_calls and the return of results, lacking production-grade elements such as a tool call execution loop, error retries and concurrency control.68% similarUnverifiedIf after the first attempt fails the operator rewrites the prompt, pastes the stack trace, or points at a suspicious file, then the two runs are no longer samples of the same process.64% similarUnverifiedWhen a path contains spaces, some scripts do not escape the spaces when concatenating command-line arguments, causing the file path to be truncated and triggering problems such as "file not found".64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1128843API
curl https://kongchang.com/api/v1/knowledge/claims/1128843MCP
get_claim(id=1128843)