Get details of a specific branch in a repository
AI agents call get_repository_branch_details to retrieve information from AtomGit 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 information about a git branch (details such as commit history, protection rules, etc.) without modifying, creating, deleting, or executing any operations. It is a pure read operation consistent with the 'Read' category for tools that retrieve or query data with no side effects.
From the tool's definition Tool name 'get_repository_branch_details' and description 'Get details of a specific branch in a repository' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_repository_branch_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AtomGit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_repository_branch_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_repository_branch_details": {}
}
} get_repository_branch_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get details of a specific branch in a repository. It is categorised as a Read tool in the AtomGit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AtomGit MCP Server MCP server in PolicyLayer and add a rule for get_repository_branch_details: 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 AtomGit MCP Server. Nothing to install.
get_repository_branch_details 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_repository_branch_details 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_repository_branch_details. 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_repository_branch_details is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AtomGit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.