get_branch
AI agents call get_branch to retrieve information from Kepler MCP GitLab Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong indicator of a read operation. Given the GitLab integration context and the presence of other tools that perform write/execute operations (create_branch, approve_merge_request, create_file), this tool almost certainly queries or retrieves branch metadata without side effects. No evidence suggests it modifies, deletes, or executes operations.
From the tool's definition Tool name 'get_branch' indicates retrieval of branch information. No description provided, but the name and context of sibling tools (which include create_branch, cherry_pick_commit, create_file) suggest this retrieves existing branch data without…
Attacks that exploit this kind of access
get_branch. It is categorised as a Read tool in the Kepler MCP GitLab Server MCP Server, which means it retrieves data without modifying state.
Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for get_branch: 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 Kepler MCP GitLab Server. Nothing to install.
get_branch 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 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. 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 is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-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 →