List and filter repository issues
AI agents call list-issues to retrieve information from GitHub Enterprise 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 queries existing issue data from a repository without creating, modifying, or deleting anything. It is a Read operation. Severity is medium rather than low because issue metadata (titles, descriptions, assignees, labels) can contain sensitive information (security vulnerabilities, internal discussions, roadmap details), and an agent with unconstrained access could enumerate and exfiltrate…
From the tool's definition Tool name is 'list-issues' and description states 'List and filter repository issues' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List and filter repository issues. It is categorised as a Read tool in the GitHub Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Enterprise 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 Enterprise 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 Enterprise MCP Server MCP server (lessinthought/github-enterprice-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 →