Extract Git repository context (branch, recent commits, status)
AI agents call get_git_context to retrieve information from Enhanced Directory Context MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and retrieves Git metadata (branch name, commit history, repository status) without modifying repositories, executing arbitrary git commands, or triggering side effects. It is a straightforward data query operation. Severity is low because reading git context poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Extract[s] Git repository context (branch, recent commits, status)' — purely retrieval operations with no modification or execution of commands.
Attacks that exploit this kind of access
Extract Git repository context (branch, recent commits, status). It is categorised as a Read tool in the Enhanced Directory Context MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Directory Context MCP Server MCP server in PolicyLayer and add a rule for get_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 Enhanced Directory Context MCP Server. Nothing to install.
get_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 get_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 get_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.
get_git_context is provided by the Enhanced Directory Context MCP Server MCP server (pwalagov/file-control-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 →