git_show_tool
AI agents call git_show_tool to retrieve information from MCP Git Commit Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_show retrieves and displays repository information without modifying state. While the description is empty, the tool name and sibling context strongly indicate read-only introspection. No data creation, deletion, execution of arbitrary code, or financial operations are implied. Confidence is high due to the unmistakable semantics of 'git show', though the empty description prevents absolute certainty.
From the tool's definition Tool name 'git_show_tool' is a standard Git command that displays commit content and metadata. Contextual pattern: server includes read-only inspection tools (git_diff_tool, git_diff_staged_tool, git_diff_unstaged_tool) alongside write/execute tools…
Attacks that exploit this kind of access
git_show_tool. It is categorised as a Read tool in the MCP Git Commit Generator MCP Server, which means it retrieves data without modifying state.
Register the MCP Git Commit Generator MCP server in PolicyLayer and add a rule for git_show_tool: 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 MCP Git Commit Generator. Nothing to install.
git_show_tool 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_show_tool 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_show_tool. 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_show_tool is provided by the MCP Git Commit Generator MCP server (luicciandev/mcp_git_commit_generator). 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 →