check_git_compliance
Validate branch state, uncommitted changes, and conventional commit compliance. Checks if on a protected branch, lists uncommitted changes, and optionally validates recent commit messages against conventional commit format (type(scope): message). Returns structured compliance report with warnings.
This record as markdown: /tools/io-github-homenshum-nodebench/check-git-compliance.md
What check_git_compliance does on Nodebench
AI agents call check_git_compliance to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_git_compliance is rated Low
This tool only inspects and validates the state of a Git repository—it examines branch status, detects uncommitted changes, and checks commit message formats. It generates a report but does not modify any data, execute code, or trigger external operations. These are purely informational read operations with no blast radius if misused by an AI agent.
From the tool's definition Tool performs validation and checking operations: 'Validate branch state, uncommitted changes', 'Checks if on a protected branch, lists uncommitted changes', 'validates recent commit messages'.
Attacks that exploit this kind of access
The rule that runs check_git_compliance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_git_compliance, this is the rule to start with:
check_git_compliance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every check_git_compliance call is checked against it from then on.
Questions about check_git_compliance
Validate branch state, uncommitted changes, and conventional commit compliance. Checks if on a protected branch, lists uncommitted changes, and optionally validates recent commit messages against conventional commit format (type(scope): message). Returns structured compliance report with warnings. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for check_git_compliance: 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 Nodebench. Nothing to install.
check_git_compliance 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_git_compliance 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_git_compliance. 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_git_compliance is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue