generate_pr_analytics_report
AI agents call generate_pr_analytics_report to retrieve information from GitHub Projects MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The server is described as a read-only data retrieval and scraping server for GitHub Projects. All sibling tools (get_project_details, get_project_iterations, get_repo_issues, get_repo_prs) are read operations. The tool name 'generate_pr_analytics_report' strongly implies generating/reading analytics data about pull requests, consistent with a Read classification.
From the tool's definition Tool name 'generate_pr_analytics_report' and server description focused on 'scraping and retrieving data from GitHub Projects'. The tool description is empty and uninformative.
Attacks that exploit this kind of access
generate_pr_analytics_report. It is categorised as a Read tool in the GitHub Projects MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for generate_pr_analytics_report: 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 Projects MCP Server. Nothing to install.
generate_pr_analytics_report 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 generate_pr_analytics_report 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 generate_pr_analytics_report. 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.
generate_pr_analytics_report is provided by the GitHub Projects MCP Server MCP server (jamescalam/github-projects-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 →