Answer: In a Copilot CLI session, enter /sandbox policy to see the effective policy for your current directory, which prints paths grouped by source and access level along with network settings and a Capabilities section. To inspect developer-tool access for a particular command, add the command after policy, for example /sandbox policy npm install. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/check-current-filesystem-policy Revision: 2 Digest: sha256:5351a625946c23d7 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:21:36Z Last changed: 2026-11-19T12:52:08Z (report contents: — → network settings and a Capabilities section) Last verified: 2026-11-20T12:58:14Z Next check: 2026-11-21T12:58:14Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of command | /sandbox policy | [1] | 2026-11-20 command with tool | /sandbox policy npm install | [1] | 2026-11-20 status command | /sandbox status | [1] | 2026-11-20 report contents | network settings and a Capabilities section | [1] | 2026-11-20 Sources: [1] GitHub. "Understanding filesystem policies for local sandboxing in GitHub Copilot CLI - GitHub Docs". https://docs.github.com/en/copilot/concepts/security-governance-and-network-settings/understanding-local-sandboxing Role: primary. Accessed: 2026-11-20T12:58:14Z Quote: "In a session, enter: Shell /sandbox policy" (Supports: command) Quote: "For example: Shell /sandbox policy npm install" (Supports: command with tool) Quote: "To check only whether sandboxing is currently on, use /sandbox status ." (Supports: status command) Quote: "The report also includes network settings and a Capabilities section covering settings such as bypass, MCP/LSP sandboxing, and authentication." (Supports: report contents) Snapshot SHA-256: 72a8f08c0ca6768e1fc573deab19d6abee48772fb9c024d8824f69d4ef23801a (captured 2026-11-18T12:52:02Z) 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:52:02Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:58:14Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:58:14Z Last attempt: 2026-11-20T12:58:14Z Notes and limitations: Extracted automatically from a single official source (section "Checking what the current policy allows"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/choose-tool-permissions How do I choose tool permissions for an agent session in the GitHub Copilot app? https://latestn.com/tool/github-copilot/permissions-and-security/cli-actions-security What security considerations should I know before using GitHub Copilot CLI in GitHub Actions? https://latestn.com/tool/github-copilot/permissions-and-security/cloud-agent-api-authentication How do I authenticate when using the GitHub Copilot cloud agent tasks API? https://latestn.com/tool/github-copilot/permissions-and-security/backend-authentication-options How do I authenticate GitHub Copilot SDK backend services using environment variable tokens, per-user OAuth tokens, or BYOK? https://latestn.com/tool/github-copilot/permissions-and-security/block-dangerous-tools-hook How do I block dangerous tools using hooks in the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/built-in-protections What built-in protections does GitHub Copilot provide for cloud agents in an enterprise? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:52:08Z | changed | report contents: — → network settings and a Capabilities section | [1] 2026-11-13T03:21:36Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/check-current-filesystem-policy/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/check-current-filesystem-policy POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/check-current-filesystem-policy with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/check-current-filesystem-policy?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I check what the current filesystem policy allows in GitHub Copilot CLI sandboxing? Revision 2, last verified 2026-11-20T12:58:14Z. https://latestn.com/tool/github-copilot/permissions-and-security/check-current-filesystem-policy (accessed 2026-11-21T09:57:20Z). @misc{LatestN_tool_github_copilot_permissions_and_security_check_current_filesystem_policy_r2, title = {How do I check what the current filesystem policy allows in GitHub Copilot CLI sandboxing?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/check-current-filesystem-policy}}, note = {Revision 2; digest sha256:5351a625946c23d7; last verified 2026-11-20T12:58:14Z; accessed 2026-11-21T09:57:20Z} } 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/check-current-filesystem-policy