list_issues
AI agents call list_issues to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list_issues' is a straightforward query operation that retrieves issue data from GitHub. Listing/querying data is a Read operation with minimal risk. Although the description is empty, the tool name is explicit enough to classify confidently. The lack of description slightly reduces confidence from maximum, but the semantic clarity is high.
From the tool's definition Tool name 'list_issues' combined with server description indicating it manages issues and provides 'native tool integration' for querying GitHub operations. The name and context clearly indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
list_issues. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for list_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 Server. Nothing to install.
list_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_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_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_issues is provided by the GitHub MCP Server MCP server (rriesco/github-mcp-server). 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 →