MCP permissions

### Describe the feature or problem you'd like to solve

add configuration allowence to usage of some tools from mcp servers

### Proposed solution

Similar
"trustedFolders": [
".",
"C:\\Users\\t0155821\\repos\\ilbs",
"C:\\Users\\t0155821\\.copilot",
"C:\\Users\\t0155821\\.config\\agents"
],
in config.json add "trustedTools": [ "mcp_server_name": ["tool_name1", "tool_name2"]]

in CLI tool there should be as well command /allow-tool

### Example prompts or workflows

especially that's useful when we always know that some mcp functionality is read-only, and cannot have negative impact, or same with side effect impact is accepted

e.g. our tool reads db, gets data from webpage , why to asks each time,

### Additional context

GitHub Copilot CLI 1.0.39

The issue points to the config.json trustedFolders pattern and the CLI’s /allow-tool command; start by tracing how MCP tools currently trigger approval prompts. Define the configuration and command behavior, then verify that listed tools can be used without repeated prompts while unlisted tools still require approval.

Escrito por el modelo de indexación a partir del texto del issue.