Show git context for the working tree: uncommitted changes annotated with index status, recent commits, and changed files. Use this at the start of a session to understand what has already been modified before searching or editing.
AI agents call git_context to retrieve information from Local Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays git repository information (uncommitted changes, recent commits, changed files). It has no side effects, does not modify any data, and is explicitly described as a read-only context tool to use 'at the start of a session' before any editing occurs.
From the tool's definition Show git context for the working tree: uncommitted changes annotated with index status, recent commits, and changed files
Documented attack patterns abuse exactly the kind of access git_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for git_context:
{
"version": "1",
"default": "deny",
"tools": {
"git_context": {}
}
}git_context 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.
Show git context for the working tree: uncommitted changes annotated with index status, recent commits, and changed files. Use this at the start of a session to understand what has already been modified before searching or editing. It is categorised as a Read tool in the Local Rag MCP Server, which means it retrieves data without modifying state.
Register the Local Rag MCP server in PolicyLayer and add a rule for git_context: 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 Rag. Nothing to install.
git_context 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_context 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_context. 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_context is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.