List and filter repository issues
AI agents call list_issues to retrieve information from GitHub See MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves issue data from a GitHub repository. It performs no mutations, executions, or destructive actions—it only retrieves information that is already public or accessible to the authenticated user. Listing issues is a safe read-only operation with minimal security risk.
From the tool's definition Tool name 'list_issues' and description 'List and filter repository issues' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List and filter repository issues. It is categorised as a Read tool in the GitHub See MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub See 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 See 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 See MCP Server MCP server (jesusmaster/github-see-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 →