git_log

Show Git commit history with author, date, and message.

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/git-log.md

WHAT IT DOES

What git_log does on Terminal Guardian

AI agents call git_log to retrieve information from Terminal Guardian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why git_log is rated Low

git_log is a standard Git command that displays commit history in a read-only manner. It queries and presents information about past commits without side effects, making it a classic Read operation. Even in a sensitive environment like a terminal-guardian MCP server, this tool only retrieves metadata and does not execute code, modify files, or alter repository state.

From the tool's definition Tool name 'git_log' and description 'Show Git commit history with author, date, and message' indicate a read-only query operation that retrieves historical metadata without modifying, executing, or deleting any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_log, this is the rule to start with:

git_log Allowed

git_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Terminal Guardian, apply this rule, and every git_log call is checked against it from then on.

FAQ

Questions about git_log

What does the git_log tool do? +

Show Git commit history with author, date, and message. It is categorised as a Read tool in the Terminal Guardian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_log? +

Register the Terminal Guardian MCP server in PolicyLayer and add a rule for git_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 Terminal Guardian. Nothing to install.

What risk level is git_log? +

git_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_log? +

Yes. Add a rate_limit block to the git_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.

How do I block git_log completely? +

Set action: deny in the PolicyLayer policy for git_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.

What MCP server provides git_log? +

git_log is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Terminal Guardian, and thousands of servers like it.

This server

All 25 Terminal Guardian tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →