get_branch_protection
AI agents call get_branch_protection 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.
This tool retrieves branch protection settings, which is a non-destructive read operation. It queries configuration state without side effects. The low severity reflects that exposure of this tool poses minimal risk—protection rules are generally non-sensitive metadata that branch administrators can view, and misuse would only result in information disclosure rather than system changes.
From the tool's definition Tool name 'get_branch_protection' indicates a retrieval operation. The 'get_' prefix is a standard convention for read-only queries. No description is provided, but the name strongly suggests querying branch protection rules rather than modifying them.
Attacks that exploit this kind of access
get_branch_protection. 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 get_branch_protection: 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.
get_branch_protection 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 get_branch_protection 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 get_branch_protection. 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.
get_branch_protection is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-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 →