Answer: Use the --allow-tool and --deny-tool options, each taking a comma-separated list of tool kinds that can optionally specify exact tools and subcommand patterns. Deny rules always take precedence over allow rules. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/allow-deny-specific-tools Revision: 1 Digest: sha256:267a86b2e1180b7e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:24:29Z Last changed: 2026-11-13T03:24:29Z Last verified: 2026-11-20T13:02:56Z Next check: 2026-11-21T13:02:56Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of allow option | --allow-tool | [1] | 2026-11-20 deny option | --deny-tool | [1] | 2026-11-20 value format | comma-separated list of tool kinds | [1] | 2026-11-20 precedence | Deny rules always take precedence over allow rules | [1] | 2026-11-20 Sources: [1] GitHub. "Allowing and denying tool use - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli/allowing-tools Role: primary. Accessed: 2026-11-20T13:02:56Z Quote: "The --allow-tool and --deny-tool options allow or deny permission for specific tools, or tool subcommands." (Supports: allow option) Quote: "If you specify a tool with --deny-tool , the AI model cannot use that tool at all" (Supports: deny option) Quote: "The value for each of these options is a comma-separated list of tool kinds, which can optionally specify exact tools and subcommand patterns." (Supports: value format) Quote: "Deny rules always take precedence over allow rules, even when --allow-all is set or a matching approval has been saved in permissions-config.json ." (Supports: precedence) Snapshot SHA-256: 703958263f3f0c60421949c2fea2792906f8e1846081691bef111d5ce814f194 (captured 2026-11-18T12:57:15Z) 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-18T12:57:15Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:02:56Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:02:56Z Last attempt: 2026-11-20T13:02:56Z Notes and limitations: Extracted automatically from a single official source (section "Allowing or denying permission for specific tools"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/allow-deny-tool-use How do I allow or deny tool use in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/permissions-and-security/allow-deny-tools How do I allow or deny specific tools in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/permissions-and-security/allow-safe-commands How do I allow safe commands to run in GitHub Copilot without manual approval? https://latestn.com/tool/github-copilot/permissions-and-security/adapt-rulesets-for-agents How do I adapt rulesets to set guardrails for GitHub Copilot cloud agents? https://latestn.com/tool/github-copilot/permissions-and-security/agentic-workflow-authentication How do I authenticate a GitHub Copilot agentic workflow using GITHUB_TOKEN or a personal access token? https://latestn.com/tool/github-copilot/permissions-and-security/agentic-workflows-security-guardrails What security guardrails does GitHub Agentic Workflows provide? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:24:29Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/allow-deny-specific-tools/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/github-copilot/permissions-and-security/allow-deny-specific-tools POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/allow-deny-specific-tools with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/allow-deny-specific-tools?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I allow or deny permission for a specific tool in GitHub Copilot CLI? Revision 1, last verified 2026-11-20T13:02:56Z. https://latestn.com/tool/github-copilot/permissions-and-security/allow-deny-specific-tools (accessed 2026-11-21T10:01:04Z). @misc{LatestN_tool_github_copilot_permissions_and_security_allow_deny_specific_tools_r1, title = {How do I allow or deny permission for a specific tool in GitHub Copilot CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/allow-deny-specific-tools}}, note = {Revision 1; digest sha256:267a86b2e1180b7e; last verified 2026-11-20T13:02:56Z; accessed 2026-11-21T10:01:04Z} } 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/github-copilot/permissions-and-security/allow-deny-specific-tools