Skip to content
AgentAtlas

GitHub Copilot CLI permissions: --allow-tool, --deny-tool, --allow-all-tools and trusted directories

How do I control which tools GitHub Copilot CLI can run without asking?

Use --allow-tool and --deny-tool with shell(COMMAND), write, or an MCP server name, or --allow-all-tools to skip all prompts. --deny-tool always beats the allow options. --allow-all or --yolo turns on all permissions at once.

Compare: allow all commands in every AI coding agent →

Compare: headless mode for scripts and CI in every AI coding agent →

The approval prompt

The first time Copilot wants a tool that can modify or execute files, it asks:

Prompt options

1. Yes
2. Yes, and approve TOOL for the rest of the running session
3. No, and tell Copilot what to do differently (Esc)

Option 2 approves that tool with any arguments for the current session only. Approving rm this way lets Copilot run any rm command until the session ends.

Allow and deny flags

  • --allow-all-tools: use any tool without approval.
  • --allow-tool: allow one tool without approval.
  • --deny-tool: block one tool. It takes precedence over both allow options.
  • Arguments: 'shell(COMMAND)', 'shell' for all shell commands, 'write' for non-shell file edits, 'MCP_SERVER_NAME' or 'MCP_SERVER_NAME(tool_name)'.
  • For git and gh you can target a first level subcommand, such as shell(git push).

Allow everything except rm and git push

copilot --allow-all-tools --deny-tool='shell(rm)' --deny-tool='shell(git push)'

Allow one MCP server but block one of its tools

copilot --allow-tool='My-MCP-Server' --deny-tool='My-MCP-Server(tool_name)'

Scripted run allowing only git

copilot -p "Show me this week's commits and summarize them" --allow-tool='shell(git)'

Turn on all permissions

--allow-all or --yolo enables all permissions at once. In an interactive session you can also control tool permissions with slash commands such as /allow-all and /yolo. Run copilot help permissions for details.

Trusted directories

At startup you confirm that you trust the launch folder and everything below it. Do not launch from your home directory. Add another folder during a session with /add-dir.

Inside Copilot CLI

/add-dir /path/to/directory

GitHub says permission scoping is heuristic and does not guarantee files outside trusted directories are protected.

Reduce risk with sandboxing

Enter /sandbox enable to restrict what commands run by Copilot can access on your machine. Or run copilot --cloud to run the whole session in an isolated cloud environment.

Sources

More GitHub Copilot guides

Reviewed Oct 23, 2026. Settings change often; the linked vendor docs are the source of truth.

Built an MCP server? Get it listed everywhere →

Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →