git_log_advanced

What git_log_advanced does on Yaver

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

Parameters from the server's own tool schema.

Why git_log_advanced is rated Low

The tool retrieves and displays git commit information with filtering capabilities. It has no capability to modify repository state, execute operations, or trigger side effects. This is a standard read operation on version control data, presenting minimal security risk. Even in a development context (Yaver is a local dev tool), git log cannot delete commits, execute code, or cause irreversible changes.

From the tool's definition Tool name 'git_log_advanced' and description 'Advanced git log with filters' indicate querying git commit history. Git log is a standard read-only operation that retrieves historical data without modifying or executing code.

Risk signalsAccepts file system path (directory)

The rule that runs git_log_advanced safely

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

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

Questions about git_log_advanced