分析 GitHub 倉庫的主要貢獻者。
AI agents call analyze_contributors 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 retrieves and analyzes existing public data about repository contributors. It performs no modifications, deletions, or external operations. It is consistent with the server's stated purpose of 'querying and analysis of public GitHub repositories' and the sibling tools (get_language_breakdown, get_repo_stats, list_recent_commits) which are all read-only operations.
From the tool's definition Tool analyzes and retrieves contributor data from GitHub repositories (implied by function name 'analyze_contributors' and server description mentioning 'contributor data').
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 analyze_contributors: 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.
analyze_contributors 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 analyze_contributors 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 analyze_contributors. 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.
analyze_contributors 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 →