List repo issues. state: open/closed/all.
AI agents call github_list_issues to retrieve information from Android 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 lists GitHub repository issues with no side effects. It is purely a read operation that queries existing data and does not create, modify, delete, or execute any operations. The low severity reflects minimal risk even if an agent lists all issues, as this information is typically public or already accessible.
From the tool's definition Tool name 'github_list_issues' and description 'List repo issues' indicate a query operation that retrieves issue data without modification. The parameter 'state: open/closed/all' is a filter on existing data.
Attacks that exploit this kind of access
List repo issues. state: open/closed/all. It is categorised as a Read tool in the Android MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for github_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 Android MCP Server. Nothing to install.
github_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 github_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 github_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.
github_list_issues is provided by the Android MCP Server MCP server (wujie272/android-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 →