analyze_git_changes

What analyze_git_changes does on Project Guardian MCP

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

Why analyze_git_changes is rated Low

This tool retrieves and examines Git state information (changed files, untracked files) within the current workspace. It performs no write, delete, or execute operations—just data inspection. The blast radius of misuse is minimal: an AI agent could at worst read what files have changed, which is non-sensitive in most secure development contexts.

From the tool's definition Tool name and description indicate it 'Analyze[s]' Git changes and untracked files—a query/inspection operation with no modification, deletion, or execution of code. The verb 'analyze' and the focus on reading workspace state confirm retrieval-only semantics.

The rule that runs analyze_git_changes safely

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

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

Questions about analyze_git_changes