Explore git commit history with formatting
AI agents call git_history_explorer to retrieve information from Claude MCP Server Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays git commit history—a read-only operation with no capability to modify, delete, or execute code. The formatting aspect is presentation of existing data. No side effects or state changes occur. Severity is low because exposure of commit history through accidental agent misuse presents minimal risk compared to other categories.
From the tool's definition Tool name 'git_history_explorer' and description 'Explore git commit history with formatting' indicate querying and viewing historical data. Uses verbs 'explore' and action is limited to examining existing commit history.
Attacks that exploit this kind of access
Explore git commit history with formatting. It is categorised as a Read tool in the Claude MCP Server Integration MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for git_history_explorer: 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 Claude MCP Server Integration. Nothing to install.
git_history_explorer 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_history_explorer 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_history_explorer. 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_history_explorer is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). 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 →