[bug] Glob and Grep tools allow directory traversal outside Location boundary #33070

Description

The Glob tool (packages/core/src/tool/glob.ts, line ~57-58) and Grep tool (packages/core/src/tool/grep.ts, line ~78) accept an optional path parameter that is passed directly to path.resolve(location.directory, input.path ?? ".") without validating whether the resolved path escapes the active Location directory.

Unlike the Read tool which uses FSUtil.contains to restrict file access within the Location boundary, Glob and Grep have no such check. The permission assertion only validates the search pattern, not the search path.

Code location

• Glob: https://github.com/anomalyco/opencode/blob/dev/packages/core/src/tool/glob.ts#L57-L58
• Grep: https://github.com/anomalyco/opencode/blob/dev/packages/core/src/tool/grep.ts#L78

Steps to reproduce

1. Open a session in any project directory
2. Call glob({ pattern: "*", path: "../../../etc" })
3. The tool returns file listings from outside the Location boundary
4. Same for grep({ pattern: ".", path: "../../../etc" })

Expected behavior

Glob and Grep should reject paths that escape the active Location, matching the behavior of the Read tool which uses FSUtil.contains.

Environment

OpenCode Desktop 1.17.8, Windows 11