[DEPRECATED] Team-level Copilot metrics are no longer available.
AI agents call get_copilot_metrics_for_team to retrieve information from Copilot Usage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though deprecated and non-functional, the tool's design intent is to retrieve (Read) GitHub Copilot usage metrics and seat assignment data. It performs no write, execute, destructive, or financial operations. Severity is low because the tool is deprecated and non-operational, eliminating practical risk.
From the tool's definition Tool name and description indicate this is a deprecated metrics retrieval endpoint. The prefix 'get_' and context as a metrics monitoring tool confirm it retrieves usage data without modification.
Attacks that exploit this kind of access
[DEPRECATED] Team-level Copilot metrics are no longer available. It is categorised as a Read tool in the Copilot Usage MCP Server, which means it retrieves data without modifying state.
Register the Copilot Usage MCP server in PolicyLayer and add a rule for get_copilot_metrics_for_team: 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 Usage. Nothing to install.
get_copilot_metrics_for_team 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 get_copilot_metrics_for_team 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 get_copilot_metrics_for_team. 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.
get_copilot_metrics_for_team is provided by the Copilot Usage MCP server (tatsuyamiyazaki/copilot-usage-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 →