List and categorize repository issues.
AI agents call get_repository_issues to retrieve information from GitHub Repository Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing issue data from a GitHub repository. It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions. The verb 'List' combined with 'categorize' (organizing existing data for display) confirms this is a read-only operation. The blast radius is minimal as misuse would only expose information already accessible to authenticated users.
From the tool's definition Tool name 'get_repository_issues' and description 'List and categorize repository issues' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
List and categorize repository issues. It is categorised as a Read tool in the GitHub Repository Analyzer MCP Server, which means it retrieves data without modifying state.
Register the GitHub Repository Analyzer MCP server in PolicyLayer and add a rule for get_repository_issues: 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 Repository Analyzer. Nothing to install.
get_repository_issues 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_repository_issues 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_repository_issues. 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_repository_issues is provided by the GitHub Repository Analyzer MCP server (jar285/github_mcp_analyzer). 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 →