changelog

What changelog does on Yaver

AI agents call changelog 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 changelog is rated Low

The changelog tool performs a read-only operation on git history. It queries git data between specified refs/tags and generates a summary. There are no side effects, no data modifications, no deletions, and no code execution triggered by the tool itself. This is a straightforward data retrieval and presentation task, characteristic of Read category tools.

From the tool's definition Tool description: 'Generate a changelog from git history between two refs/tags.' This reads and queries git history to produce a changelog output; it retrieves information without modifying, deleting, or executing external operations.

Risk signalsAccepts file system path (directory)

The rule that runs changelog 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 changelog, this is the rule to start with:

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

Questions about changelog