Add setting to restrict actions to the current repo

[simone-viozzi]

Describe the feature or problem you’d like to solve

If I ask copilot to pull the issues, or create a new issue, it is possible that it uses the wrong owner / repo and pull random issues or tries to create issues on non-existing repos.

Then after an error, it runs git remote -v or calls the tool get_me and re-does the action.

For now, it never happened that it created issues on other people repos, but it would like to exclude the possibility entirely.

Proposed solution

Add a setting to restrict all actions to the current repo.
This would remove the "owner" and "repo" from all tool calls.

Example prompts or workflows (for tools/toolsets only)

Additional context

For example, the "add comment to issue" tool would become:

{
  "body":  "....",
  "issue_number": 109
}

[almaleksia]

Hi @simone-viozzi, you can achieve that by accessing MCP with fine-grained token with permissions limited to one repo.

[simone-viozzi]

How do I set the token in the MCP server?

I have the server declared in mcp.json

"github": {
    "type": "http",
    "url": "https://api.githubcopilot.com/mcp/"
}

Also restricting copilot to a single repo will still lead to copilot trying to fetch issues from random repos, just this time it will always fail.

I would like to address the root cause of the problem and remove the owner and repo parameters from the MCP calls, so that there cannot be any wrong value.