Check if a git branch name follows conventions (issue ID prefix, kebab-case)
AI agents call review_branch_name to retrieve information from Engineering Standards without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a validation/inspection tool that reads and analyzes git branch naming patterns. It has no side effects, does not execute code, does not modify git state, and does not delete or create branches. It is purely informational—checking conformance to engineering standards. The severity is low because misuse would only provide false feedback about naming conventions, with no operational impact.
From the tool's definition The tool 'review_branch_name' checks if a git branch name follows conventions; it validates and inspects existing branch names against standards without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Check if a git branch name follows conventions (issue ID prefix, kebab-case). It is categorised as a Read tool in the Engineering Standards MCP Server, which means it retrieves data without modifying state.
Register the Engineering Standards MCP server in PolicyLayer and add a rule for review_branch_name: 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 Engineering Standards. Nothing to install.
review_branch_name 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 review_branch_name 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 review_branch_name. 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.
review_branch_name is provided by the Engineering Standards MCP server (rajgurung/claude-engineering-standards). 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 →