Generate release notes / changelog from git commit history between two refs. Analyzes commits between two refs (tags, SHAs, or branches) and produces a formatted changelog. Supports three output formats: Keep a Changelog (keepachangelog), GitHub Release (github-release), and plain text. Auto-dete...
AI agents call generate_changelog to retrieve information from Pr Narrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and analyzes existing git commit history to produce formatted output. It does not modify any data, execute commands, or have side effects — it is purely a read/query operation over git refs.
From the tool's definition Generate release notes / changelog from git commit history between two refs. Analyzes commits between two refs (tags, SHAs, or branches) and produces a formatted changelog.
Attacks that exploit this kind of access
Generate release notes / changelog from git commit history between two refs. Analyzes commits between two refs (tags, SHAs, or branches) and produces a formatted changelog. Supports three output formats: Keep a Changelog (keepachangelog), GitHub Release (github-release), and plain text. Auto-detects: - Latest tag as the start ref if not provided - Conventional commit types and scopes - Non-conventional commit types via keyword inference - Co-authors from commit trailers - Ticket references from commit messages Use this when a user wants to generate release notes, changelogs, or understand what changed between two versions. It is categorised as a Read tool in the Pr Narrator MCP Server, which means it retrieves data without modifying state.
Register the Pr Narrator MCP server in PolicyLayer and add a rule for generate_changelog: 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 Pr Narrator. Nothing to install.
generate_changelog 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 generate_changelog 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 generate_changelog. 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.
generate_changelog is provided by the Pr Narrator MCP server (mhaviv/pr-narrator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →