AI agents call git_docs to retrieve information from Git without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs documentation searches and browsing—purely informational operations. It retrieves static reference material without modifying any Git repositories, code, or system state. No destructive, financial, or code execution capabilities are present. The low severity reflects minimal risk even if an AI agent misuses this tool, as the worst outcome would be retrieving irrelevant documentation.
From the tool's definition Tool name 'git_docs' and description 'Search and browse official Git documentation from git-scm.com' indicate read-only information retrieval with no side effects.
Attacks that exploit this kind of access
Search and browse official Git documentation from git-scm.com. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git MCP server in PolicyLayer and add a rule for git_docs: 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 Git. Nothing to install.
git_docs 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_docs 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_docs. 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_docs is provided by the Git MCP server (selfagency/git-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 →