git_check_if_repo
AI agents call git_check_if_repo to retrieve information from Test MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it performs a read-only check (is this directory a git repository?), which is a query operation with no side effects. It aligns with Read category behavior. However, the empty description prevents higher confidence. The low severity reflects minimal blast radius—an agent misusing this would only retrieve information about whether a directory is a repository.
From the tool's definition Tool name 'git_check_if_repo' indicates a query operation that checks repository status without modifying state. Empty description lowers confidence.
Attacks that exploit this kind of access
git_check_if_repo. It is categorised as a Read tool in the Test MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Test MCP Server MCP server in PolicyLayer and add a rule for git_check_if_repo: 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 Test MCP Server. Nothing to install.
git_check_if_repo 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_check_if_repo 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_check_if_repo. 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_check_if_repo is provided by the Test MCP Server MCP server (jojodiaz/mcp-local-context). 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 →