取得 GitHub 倉庫的程式語言分布統計。
AI agents call get_language_breakdown to retrieve information from GitHub Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns statistical data about language composition in a repository—a non-mutating read operation. There are no side effects, no code execution, no data modification, and no destructive actions. The low severity reflects that unauthorized access to public repository metadata poses minimal risk.
From the tool's definition Tool retrieves 'programming language distribution statistics' from GitHub repositories. The description indicates data retrieval and analysis ('取得...統計' = 'obtain/retrieve statistics') with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
取得 GitHub 倉庫的程式語言分布統計。. It is categorised as a Read tool in the GitHub Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Analytics MCP Server MCP server in PolicyLayer and add a rule for get_language_breakdown: 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 Analytics MCP Server. Nothing to install.
get_language_breakdown 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_language_breakdown 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_language_breakdown. 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_language_breakdown is provided by the GitHub Analytics MCP Server MCP server (pyroxyl/github-analytics-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 →