Shows the working tree status.
AI agents call git_status_tool to retrieve information from MCP Git Commit Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation analogous to 'git status', which displays the current state of the working directory and staging area. It has no side effects, does not modify data, and poses minimal risk if misused by an AI agent. The low severity reflects that status queries cannot harm the repository or trigger unintended operations.
From the tool's definition Tool name 'git_status_tool' and description 'Shows the working tree status' indicate a query operation that retrieves repository state information without modifying or executing changes.
Attacks that exploit this kind of access
Shows the working tree status. It is categorised as a Read tool in the MCP Git Commit Generator MCP Server, which means it retrieves data without modifying state.
Register the MCP Git Commit Generator MCP server in PolicyLayer and add a rule for git_status_tool: 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 MCP Git Commit Generator. Nothing to install.
git_status_tool 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 git_status_tool 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 git_status_tool. 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.
git_status_tool is provided by the MCP Git Commit Generator MCP server (luicciandev/mcp_git_commit_generator). 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 →