Get repository status. Shows the working tree status including tracked/untracked files, modifications, staged changes, and current branch information.
AI agents call git_status to retrieve information from Git MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_status purely retrieves status information about a Git repository's current state. It has no side effects, does not modify data, execute code, delete anything, or move money. This is a straightforward Read operation with minimal security risk—the worst case is an AI agent learning what files exist or have been changed, which is informational only.
From the tool's definition Tool name 'git_status' and description 'Get repository status. Shows the working tree status including tracked/untracked files, modifications, staged changes, and current branch information' indicate a query operation that retrieves and displays information…
Attacks that exploit this kind of access
Get repository status. Shows the working tree status including tracked/untracked files, modifications, staged changes, and current branch information. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_status: 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 Git MCP Server. Nothing to install.
git_status 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 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. 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 is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). 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 →