Answer: You restrict which tools Gemini CLI users can access by using the `tools.core` setting and the Policy Engine, with allowlisting via `coreTools` being the most secure approach. You can also disable YOLO mode at the policy level to prevent tool execution without user approval. Status: Confirmed Entry: tool/gemini-cli/permissions-and-security/restrict-tool-access Revision: 1 Digest: sha256:b3a5e6eca56ed545 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:17:26Z Last changed: 2026-11-13T03:17:26Z Last verified: 2026-11-20T12:50:49Z Next check: 2026-11-21T12:50:49Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of setting | tools.core | [1] | 2026-11-20 allowlist example | ["ReadFileTool", "GlobTool", "ShellTool(ls)"] | [1] | 2026-11-20 blocklist setting | excludeTools | [1] | 2026-11-20 disable YOLO setting | disableYoloMode | [1] | 2026-11-20 Sources: [1] Google. "Gemini CLI for the enterprise". https://geminicli.com/docs/cli/enterprise.md Role: primary. Accessed: 2026-11-20T12:50:49Z Quote: "This is achieved through the `tools.core` setting and the" (Supports: setting) Quote: ""core": ["ReadFileTool", "GlobTool", "ShellTool(ls)"]" (Supports: allowlist example) Quote: "### Blocklisting with `excludeTools` (Deprecated)" (Supports: blocklist setting) Quote: ""disableYoloMode": true" (Supports: disable YOLO setting) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: 1ad16859c14ea8134e9192516a53b09c4df38965dd637fac219e262ac35417d1 (captured 2026-11-13T03:17:26Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:17:26Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:50:49Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:50:49Z Last attempt: 2026-11-20T12:50:49Z Notes and limitations: Extracted automatically from a single official source (section "Restricting tool access"). Related: https://latestn.com/tool/gemini-cli/permissions-and-security/rule-matching-priority How does Gemini CLI match policy rules and resolve conflicts using priority tiers? https://latestn.com/tool/gemini-cli/permissions-and-security/sandbox-expansion-outside-workspace How do I include files outside the workspace in the Gemini CLI sandbox? https://latestn.com/tool/gemini-cli/permissions-and-security/sandbox-proxy-script-setup How do I configure a proxy script for the Gemini CLI sandbox using GEMINI_SANDBOX_PROXY_COMMAND? https://latestn.com/tool/gemini-cli/permissions-and-security/plan-mode-yolo-availability Is Gemini CLI's enter_plan_mode tool available in YOLO mode? https://latestn.com/tool/gemini-cli/permissions-and-security/proxy-allowed-domains How do I restrict which domains the Gemini CLI sandbox proxy allows? https://latestn.com/tool/gemini-cli/permissions-and-security/remote-subagent-authentication How do I configure authentication for a remote subagent in Gemini CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:17:26Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/permissions-and-security/restrict-tool-access/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/restrict-tool-access POST: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/restrict-tool-access with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/restrict-tool-access?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I restrict which tools Gemini CLI users can access? Revision 1, last verified 2026-11-20T12:50:49Z. https://latestn.com/tool/gemini-cli/permissions-and-security/restrict-tool-access (accessed 2026-11-21T09:58:14Z). @misc{LatestN_tool_gemini_cli_permissions_and_security_restrict_tool_access_r1, title = {How do I restrict which tools Gemini CLI users can access?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/permissions-and-security/restrict-tool-access}}, note = {Revision 1; digest sha256:b3a5e6eca56ed545; last verified 2026-11-20T12:50:49Z; accessed 2026-11-21T09:58:14Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/gemini-cli/permissions-and-security/restrict-tool-access