Get Copilot user-level metrics for a GitHub Enterprise.
AI agents call get_copilot_user_metrics_for_enterprise 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.
This tool queries and retrieves existing usage metrics without side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could only gain visibility into Copilot usage data, which is informational and non-destructive.
From the tool's definition Tool retrieves 'user-level metrics' for GitHub Enterprise; the description uses read-only language ('Get') with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Get Copilot user-level metrics for a GitHub Enterprise. 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_user_metrics_for_enterprise: 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_user_metrics_for_enterprise 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_user_metrics_for_enterprise 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_user_metrics_for_enterprise. 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_user_metrics_for_enterprise 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 →