Show the working tree status of a git repository.
AI agents call git_status to retrieve information from DevToolkit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_status retrieves and displays the current state of a git working directory (untracked files, modifications, staged changes) without creating, modifying, deleting, or executing anything. It is a standard diagnostic read operation commonly used in development workflows. Low severity because the blast radius of misuse is minimal—exposing repository state information poses no direct operational risk.
From the tool's definition Tool description states 'Show the working tree status of a git repository' — a query operation with no modification or execution of code. The verb 'show' and the information-retrieval nature of git status confirm read-only semantics.
Attacks that exploit this kind of access
Show the working tree status of a git repository. It is categorised as a Read tool in the DevToolkit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevToolkit 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 DevToolkit 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 DevToolkit MCP Server MCP server (tusharrayamajhi/devtoolkit-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 →