Check if current directory is a Git repository.
AI agents call checkGitRepository to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple status check by verifying whether the current directory is a Git repository. It retrieves information about the local environment without creating, modifying, deleting, or executing anything. This is a non-destructive read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'checkGitRepository' and description 'Check if current directory is a Git repository' indicate a query/verification operation with no data modification or side effects.
Attacks that exploit this kind of access
Check if current directory is a Git repository. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for checkGitRepository: 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 GitHub MCP Server. Nothing to install.
checkGitRepository 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 checkGitRepository 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 checkGitRepository. 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.
checkGitRepository is provided by the GitHub MCP Server MCP server (j-nowcow/github-mcp-practice). 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 →