copilot_suggest_gh
AI agents invoke copilot_suggest_gh to trigger actions in GitHub Copilot CLI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The description is empty, lowering confidence. Based on the server description and sibling tools, this tool likely suggests GitHub CLI (gh) commands. Suggestions alone would be Read, but GitHub CLI commands can execute operations like creating PRs, managing repos, triggering workflows — making misuse potentially high severity.
From the tool's definition Tool name 'copilot_suggest_gh' and server context wrapping GitHub Copilot CLI for natural language command suggestions for GitHub CLI commands
Attacks that exploit this kind of access
copilot_suggest_gh. It is categorised as a Execute tool in the GitHub Copilot CLI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GitHub Copilot CLI MCP Server MCP server in PolicyLayer and add a rule for copilot_suggest_gh: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GitHub Copilot CLI MCP Server. Nothing to install.
copilot_suggest_gh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the copilot_suggest_gh rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for copilot_suggest_gh. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
copilot_suggest_gh is provided by the GitHub Copilot CLI MCP Server MCP server (wminson/copilot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →