List issues in a GitHub repository
AI agents call list_repo_issues to retrieve information from GitHub MCP TypeScript SDK 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 queries existing GitHub issues from a repository. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval function, placing it in the Read category with low severity since unauthorized access to public repository issues poses minimal risk, and even private repository access is typically controlled by GitHub's authentication…
From the tool's definition Tool name 'list_repo_issues' and description 'List issues in a GitHub repository' indicate a retrieval operation.
Attacks that exploit this kind of access
List issues in a GitHub repository. It is categorised as a Read tool in the GitHub MCP TypeScript SDK Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP TypeScript SDK Server MCP server in PolicyLayer and add a rule for list_repo_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 MCP TypeScript SDK Server. Nothing to install.
list_repo_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 list_repo_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 list_repo_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.
list_repo_issues is provided by the GitHub MCP TypeScript SDK Server MCP server (om-shree-0709/github-mcp-ts-sdk). 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 →