Get code suggestions and completions from GitHub Copilot
AI agents call copilot_suggest to retrieve information from Copilot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
copilot_suggest performs a query operation that returns code suggestions/completions. It does not create, modify, execute, delete, or move data. The suggestions are informational output only, with no side effects on the codebase or external systems. This is analogous to a search or fetch operation, classifying it as Read with low severity.
From the tool's definition Tool description states 'Get code suggestions and completions from GitHub Copilot' — this retrieves AI-generated suggestions without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get code suggestions and completions from GitHub Copilot. It is categorised as a Read tool in the Copilot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Copilot MCP Server MCP server in PolicyLayer and add a rule for copilot_suggest: 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 Copilot MCP Server. Nothing to install.
copilot_suggest is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the copilot_suggest 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. 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 is provided by the Copilot MCP Server MCP server (willianpaiva/copilot-mcp). 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 →