AI agents call git_status to retrieve information from Mcp Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports Git repository metadata (branch, file states). It has no side effects, makes no modifications, executes no code, and poses minimal risk. It is a pure read operation, consistent with the 'Read' category for tools that retrieve or query data. Severity is low because misuse would only expose local repository state information.
From the tool's definition Tool name 'git_status' and description 'Report the Git state: current branch, staged/modified/untracked' indicate a query operation that retrieves repository state information without modifying or executing anything.
Attacks that exploit this kind of access
Report the Git state: current branch, staged/modified/untracked. It is categorised as a Read tool in the Mcp Flow MCP Server, which means it retrieves data without modifying state.
Register the Mcp Flow 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 Mcp Flow. 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 Mcp Flow MCP server (remimenguy/mcp-flow). 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 →