Skip to content

Address security question about Git MCP server permissions#168

Closed
Copilot wants to merge 1 commit intotest-mcpfrom
copilot/sub-pr-163
Closed

Address security question about Git MCP server permissions#168
Copilot wants to merge 1 commit intotest-mcpfrom
copilot/sub-pr-163

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Jan 8, 2026

Clarified that the Git MCP server configured in .github/mcp/mcp-config.json does not grant Copilot privileges to alter the main branch directly.

Response Summary

The Git MCP server provides local-only Git operations:

  • Status, diff, log viewing
  • Local commits and branch management
  • No inherent push permissions

Protection mechanisms that remain enforced:

  • GitHub repository permissions
  • Branch protection rules on main
  • Standard PR workflow requirements
  • GITHUB_TOKEN scope limitations (separate from Git server)

The server is a read-mostly tool for local version control. All remote operations remain subject to GitHub's standard access controls.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI mentioned this pull request Jan 8, 2026
Copilot AI changed the title [WIP] Update address feedback on server permissions for Copilot Address security question about Git MCP server permissions Jan 8, 2026
Copilot AI requested a review from d-morrison January 8, 2026 05:44
@d-morrison d-morrison closed this Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants