Answer: Set tool policies per-tool when creating an agent using the toolPolicies option: use { autoApprove: true } to auto-approve a tool and { autoApprove: false } to require approval before it runs. Status: Confirmed Entry: tool/cline/permissions-and-security/set-tool-policies Revision: 1 Digest: sha256:c519a2e0a0140f0f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:40Z Last changed: 2026-11-13T03:07:40Z Last verified: 2026-11-20T12:30:40Z Next check: 2026-11-21T12:30:40Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Auto-approve policy | { autoApprove: true } | [1] | 2026-11-20 Require approval policy | { autoApprove: false } | [1] | 2026-11-20 Disable policy | { enabled: false } | [1] | 2026-11-20 Default with no policy | Defaults to enabled and auto-approved | [1] | 2026-11-20 Example auto-approve read_files | read_files: { autoApprove: true } | [1] | 2026-11-20 Example require approval editor | editor: { autoApprove: false } | [1] | 2026-11-20 Sources: [1] Cline. "Permission Handling". https://docs.cline.bot/sdk/guides/permission-handling.md Role: primary. Accessed: 2026-11-20T12:30:40Z Quote: "| `{ autoApprove: true }` | Tool executes immediately without approval |" (Supports: Auto-approve policy) Quote: "| `{ autoApprove: false }` | Tool waits for approval before executing |" (Supports: Require approval policy) Quote: "| `{ enabled: false }` | Tool is completely disabled (model won't see it) |" (Supports: Disable policy) Quote: "| No policy set | Defaults to enabled and auto-approved |" (Supports: Default with no policy) Quote: "read_files: { autoApprove: true }, // Always run without asking" (Supports: Example auto-approve read_files) Quote: "editor: { autoApprove: false }, // Always ask before running" (Supports: Example require approval editor) Published: 2026-11-20T00:16:32Z Snapshot SHA-256: fdb4601c071508d522a037490532aa597459bdd10e130d4d8cb7b2272d7dc5ea (captured 2026-11-13T03:07:40Z) 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:40Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:40Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:40Z Last attempt: 2026-11-20T12:30:40Z Notes and limitations: Extracted automatically from a single official source (section "Tool Policies"). Related: 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/cline/permissions-and-security/safe-vs-approval-required-commands How does Cline decide which terminal commands are safe versus requiring approval? https://latestn.com/tool/cline/permissions-and-security/sandbox-tool-execution How do I sandbox tool execution for security when deploying Cline agents to production? https://latestn.com/tool/cline/permissions-and-security/secure-api-key-storage How do I securely store my Cline API key using environment variables or a .env file? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/permissions-and-security/set-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/set-tool-policies POST: https://latestn.com/dispute/tool/cline/permissions-and-security/set-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/set-tool-policies?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set tool policies to auto-approve or require approval for tools in Cline? Revision 1, last verified 2026-11-20T12:30:40Z. https://latestn.com/tool/cline/permissions-and-security/set-tool-policies (accessed 2026-11-21T10:04:30Z). @misc{LatestN_tool_cline_permissions_and_security_set_tool_policies_r1, title = {How do I set tool policies to auto-approve or require approval for tools in Cline?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/permissions-and-security/set-tool-policies}}, note = {Revision 1; digest sha256:c519a2e0a0140f0f; last verified 2026-11-20T12:30:40Z; accessed 2026-11-21T10:04:30Z} } 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/set-tool-policies