Get the current branch for a single repo by its label or path.
AI agents call check_repo_branch to retrieve information from Agentic Bits Claude Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a repository's current branch state without modifying any data, triggering external operations, deleting content, or moving money. It is a straightforward query operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states 'Get the current branch for a single repo' - this is a retrieval operation with no modification or side effects. The verb 'get' and the action of querying repository state confirm a read-only operation.
Attacks that exploit this kind of access
Get the current branch for a single repo by its label or path. It is categorised as a Read tool in the Agentic Bits Claude Plugin MCP Server, which means it retrieves data without modifying state.
Register the Agentic Bits Claude Plugin MCP server in PolicyLayer and add a rule for check_repo_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 Agentic Bits Claude Plugin. Nothing to install.
check_repo_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 check_repo_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 check_repo_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.
check_repo_branch is provided by the Agentic Bits Claude Plugin MCP server (onesmartguy/agentic-bits-claude-plugin). 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 →