Answer: Tool Policies control whether a tool is visible and whether it requires approval. Setting `{ autoApprove: true }` runs without asking, `{ autoApprove: false }` asks before running, and `{ enabled: false }` hides/disables the tool; tool names not listed in `toolPolicies` default to enabled and auto-approved. Status: Confirmed Entry: tool/cline/permissions-and-security/tool-policies Revision: 1 Digest: sha256:051348a41306d27e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:54Z Last changed: 2026-11-13T03:07:54Z Last verified: 2026-11-20T12:31:16Z Next check: 2026-11-21T12:31:16Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of autoApprove true | Run without asking | [1] | 2026-11-20 autoApprove false | Ask before running | [1] | 2026-11-20 enabled false | Hide/disable the tool | [1] | 2026-11-20 default behavior | default to enabled and auto-approved | [1] | 2026-11-20 Sources: [1] Cline. "Tools". https://docs.cline.bot/sdk/tools.md Role: primary. Accessed: 2026-11-20T12:31:16Z Quote: "| `{ autoApprove: true }` | Run without asking |" (Supports: autoApprove true) Quote: "| `{ autoApprove: false }` | Ask before running |" (Supports: autoApprove false) Quote: "| `{ enabled: false }` | Hide/disable the tool |" (Supports: enabled false) Quote: "Tool names not listed in `toolPolicies` default to enabled and auto-approved." (Supports: default behavior) Published: 2026-11-20T06:00:24Z Snapshot SHA-256: e6af2d4bfa8753d6f4ae0e2b0f2612ad387e53bfface1f80658c1e86bdef54fb (captured 2026-11-13T03:07:53Z) 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:07:54Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:31:16Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:31:16Z Last attempt: 2026-11-20T12:31:16Z Notes and limitations: Extracted automatically from a single official source (section "Tool Policies"). Related: https://latestn.com/tool/cline/permissions-and-security/tool-rejected-behavior What happens in Cline when a tool is rejected? https://latestn.com/tool/cline/permissions-and-security/yolo-mode-auto-approved-actions Which actions does Cline auto-approve in YOLO mode? https://latestn.com/tool/cline/permissions-and-security/yolo-mode-risks-best-practices What are the risks and best practices for using YOLO mode in Cline? https://latestn.com/tool/cline/permissions-and-security/subagent-approvals How do approvals work for Cline subagents? https://latestn.com/tool/cline/permissions-and-security/tool-approval-callbacks How do I set up tool approval callbacks in ClineCore? https://latestn.com/tool/cline/permissions-and-security/tool-approval-policy-controls How do I control tool approval and policy settings in Cline? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:54Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/permissions-and-security/tool-policies/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/cline/permissions-and-security/tool-policies POST: https://latestn.com/dispute/tool/cline/permissions-and-security/tool-policies with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/permissions-and-security/tool-policies?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do tool policies work in Cline? Revision 1, last verified 2026-11-20T12:31:16Z. https://latestn.com/tool/cline/permissions-and-security/tool-policies (accessed 2026-11-21T10:08:21Z). @misc{LatestN_tool_cline_permissions_and_security_tool_policies_r1, title = {How do tool policies work in Cline?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/permissions-and-security/tool-policies}}, note = {Revision 1; digest sha256:051348a41306d27e; last verified 2026-11-20T12:31:16Z; accessed 2026-11-21T10:08:21Z} } 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/cline/permissions-and-security/tool-policies