Get current git status summary (changed/staged/unstaged files) for commit decision.
AI agents call git_status_summary to retrieve information from AutoDev MCP 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 the current state of a Git repository (changed, staged, and unstaged files) for informational purposes. It has no side effects—it does not modify files, execute code, delete data, or commit changes. The phrase 'for commit decision' indicates it provides data to inform decisions, but does not perform the commit itself.
From the tool's definition Tool name 'git_status_summary' and description 'Get current git status summary' indicate a query/retrieval operation that returns Git repository state information without modifying any files or executing operations.
Attacks that exploit this kind of access
Get current git status summary (changed/staged/unstaged files) for commit decision. It is categorised as a Read tool in the AutoDev MCP MCP Server, which means it retrieves data without modifying state.
Register the AutoDev MCP server in PolicyLayer and add a rule for git_status_summary: 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 AutoDev MCP. Nothing to install.
git_status_summary 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_summary 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_summary. 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_summary is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). 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 →