Run git status --short in an allowed project root.
AI agents call mcp_git_status to retrieve information from Local Code without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git status is a non-mutating query that retrieves information about the working directory and index state. It has no side effects on code, configuration, or git history. Execution is confined to allowed project roots per the server design. While 'Execute' might be considered since it runs a git command, the actual effect is purely informational—no data is created, modified, deleted, or committed.
From the tool's definition Tool runs 'git status --short', which queries git state and reports file changes without modifying repository or files. The server description emphasizes 'list, read, search' operations and mentions 'dry-run diffs', indicating read-only introspection.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Run git status --short in an allowed project root. It is categorised as a Read tool in the Local Code MCP Server, which means it retrieves data without modifying state.
Register the Local Code MCP server in PolicyLayer and add a rule for mcp_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 Local Code. Nothing to install.
mcp_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 mcp_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 mcp_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.
mcp_git_status is provided by the Local Code MCP server (js190-prog/local-code-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 →