Get the current git status of a repository. Shows modified, untracked, and staged files.\n\n
AI agents call git_status to retrieve information from Aider 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 repository metadata (file states, staging area status). It has no side effects, no destructive capability, and no ability to modify or execute code. The operation is purely informational and read-only, consistent with the Read category for tools that retrieve data without side effects.
From the tool's definition Tool description states 'Get the current git status of a repository. Shows modified, untracked, and staged files.' This is a query operation that retrieves information about repository state without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access git_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aider MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for git_status:
{
"version": "1",
"default": "deny",
"tools": {
"git_status": {}
}
}git_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current git status of a repository. Shows modified, untracked, and staged files.\n\n. It is categorised as a Read tool in the Aider MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Aider 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 Aider 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 Aider MCP Server MCP server (sengokudaikon/aider-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Aider MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Aider MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.