This record as markdown: /tools/io-github-dave-london-git/log.md
What log does on Git
AI agents call log to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why log is rated Low
This tool only queries and retrieves existing commit history in a structured JSON format. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could only gain visibility into repository history, which is typically non-sensitive or already accessible within the repository's permission model.
From the tool's definition Tool name 'log' and description 'Returns commit history as structured data' indicate read-only retrieval of git commit history with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log, this is the rule to start with:
log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every log call is checked against it from then on.
Questions about log
Returns commit history as structured data. 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 log: 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.
log 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 log 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 log. 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.
log is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue