diff options
| author | Will 保哥 <[email protected]> | 2025-06-30 02:43:27 +0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2025-06-29 18:43:27 +0000 |
| commit | 91502193ec0883dc00a90a491218d0ac5f5c0ff1 (patch) | |
| tree | 9d630451047585fac5cb70ea32f0199e6c3d3539 | |
| parent | c860dac2333320d53a9bb9054efe460b8798fc2b (diff) | |
Fix a broken link (#2598)
| -rw-r--r-- | docs/tools/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tools/index.md b/docs/tools/index.md index 85aec424..4fa98c03 100644 --- a/docs/tools/index.md +++ b/docs/tools/index.md @@ -35,7 +35,7 @@ You will typically see messages in the CLI indicating when a tool is being calle Many tools, especially those that can modify your file system or execute commands (`write_file`, `edit`, `run_shell_command`), are designed with safety in mind. The Gemini CLI will typically: - **Require confirmation:** Prompt you before executing potentially sensitive operations, showing you what action is about to be taken. -- **Utilize sandboxing:** All tools are subject to restrictions enforced by sandboxing (see [README](../../README.md#sandboxing)). This means that when operating in a sandbox, any tools (including MCP servers) you wish to use must be available _inside_ the sandbox environment. For example, to run an MCP server through `npx`, the `npx` executable must be installed within the sandbox's Docker image or be available in the `sandbox-exec` environment. +- **Utilize sandboxing:** All tools are subject to restrictions enforced by sandboxing (see [Sandboxing in the Gemini CLI](../sandbox.md)). This means that when operating in a sandbox, any tools (including MCP servers) you wish to use must be available _inside_ the sandbox environment. For example, to run an MCP server through `npx`, the `npx` executable must be installed within the sandbox's Docker image or be available in the `sandbox-exec` environment. It's important to always review confirmation prompts carefully before allowing a tool to proceed. |