Answer: You can use tool policies for simple cases, or use `requestToolApproval` when your application needs to decide dynamically. The callback is defined in the `capabilities` object passed to `ClineCore.create`, returning an approval decision such as `{ approved: request.toolName !== "run_commands" }`. Status: Confirmed Entry: tool/cline/permissions-and-security/tool-approval-callbacks Revision: 1 Digest: sha256:48d9a1b39ec93c5b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:33Z Last changed: 2026-11-13T03:07:33Z Last verified: 2026-11-20T12:30:22Z Next check: 2026-11-21T12:30:22Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Dynamic approval callback | requestToolApproval | [1] | 2026-11-20 Callback location | capabilities | [1] | 2026-11-20 Example approval return | { approved: request.toolName !== "run_commands" } | [1] | 2026-11-20 Simple policy option | toolPolicies | [1] | 2026-11-20 Auto-approve example | read_files: { autoApprove: true } | [1] | 2026-11-20 Sources: [1] Cline. "ClineCore". https://docs.cline.bot/sdk/clinecore.md Role: primary. Accessed: 2026-11-20T12:30:22Z Quote: "Use `requestToolApproval` when your application needs to decide dynamically:" (Supports: Dynamic approval callback) Quote: "capabilities: { requestToolApproval: async (request) => {" (Supports: Callback location) Quote: "return { approved: request.toolName !== "run_commands" }" (Supports: Example approval return) Quote: "toolPolicies: {" (Supports: Simple policy option) Quote: "read_files: { autoApprove: true }," (Supports: Auto-approve example) Published: 2026-11-20T00:16:31Z Snapshot SHA-256: f740b4a5ddcca087d35a91045f5ebc131b2d957a893dc55cc9db1d6fe3b9a2a9 (captured 2026-11-13T03:07:33Z) 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:33Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:22Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:22Z Last attempt: 2026-11-20T12:30:22Z Notes and limitations: Extracted automatically from a single official source (section "Tool Approval"). Related: 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/tool-policies How do tool policies work in Cline? 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/secure-api-key-storage How do I securely store my Cline API key using environment variables or a .env file? https://latestn.com/tool/cline/permissions-and-security/set-tool-policies How do I set tool policies to auto-approve or require approval for tools in Cline? https://latestn.com/tool/cline/permissions-and-security/subagent-approvals How do approvals work for Cline subagents? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:33Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/permissions-and-security/tool-approval-callbacks/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-approval-callbacks POST: https://latestn.com/dispute/tool/cline/permissions-and-security/tool-approval-callbacks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/permissions-and-security/tool-approval-callbacks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set up tool approval callbacks in ClineCore? Revision 1, last verified 2026-11-20T12:30:22Z. https://latestn.com/tool/cline/permissions-and-security/tool-approval-callbacks (accessed 2026-11-21T10:06:26Z). @misc{LatestN_tool_cline_permissions_and_security_tool_approval_callbacks_r1, title = {How do I set up tool approval callbacks in ClineCore?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/permissions-and-security/tool-approval-callbacks}}, note = {Revision 1; digest sha256:48d9a1b39ec93c5b; last verified 2026-11-20T12:30:22Z; accessed 2026-11-21T10:06:26Z} } 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-approval-callbacks