List repo branches.
AI agents call github_list_branches 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 performs a read-only query against a repository to enumerate branches. It has no side effects, does not execute code, does not modify data, and does not access or manipulate sensitive Android system resources. It is a straightforward data retrieval operation typical of version control system queries, fitting the Read category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate a query operation: 'List repo branches' retrieves branch information without modifying state.
Attacks that exploit this kind of access
List repo branches. 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_branches: 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_branches 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_branches 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_branches. 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_branches 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 →