AI agents call git_show to retrieve information from Coding Tools MCP 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 historical commit information such as diffs, logs, and file contents. It has no side effects, does not execute code, and does not modify the repository. While the tool operates in an engineering context with exec_command and patch tools also present, git_show itself performs only data retrieval.
From the tool's definition Tool name 'git_show' is a standard Git command that displays commit contents, diffs, and metadata without modifying any data.
Documented attack patterns abuse exactly the kind of access git_show gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coding Tools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for git_show:
{
"version": "1",
"default": "deny",
"tools": {
"git_show": {}
}
}git_show is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
git_show. It is categorised as a Read tool in the Coding Tools MCP MCP Server, which means it retrieves data without modifying state.
Register the Coding Tools MCP server in PolicyLayer and add a rule for git_show: 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 Coding Tools MCP. Nothing to install.
git_show 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 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. 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 is provided by the Coding Tools MCP server (xytom/coding-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Coding Tools MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Coding Tools MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.