AI agents call generate_release_notes to retrieve information from Tickr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
release_id | string | Yes | UUID of the release |
Parameters from the server's own tool schema.
The tool reads linked tickets and generates markdown content client-side. It produces output (release notes) but does not persist, modify, or delete any data. 'Client-side generation' confirms no server-side writes occur. This is a read/query operation that formats existing data into a document.
From the tool's definition Generate markdown release notes from linked tickets (client-side generation)
Attacks that exploit this kind of access
Generate markdown release notes from linked tickets (client-side generation). It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
generate_release_notes accepts 2 parameters: project, release_id. Required: project, release_id. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for generate_release_notes: 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 Tickr. Nothing to install.
generate_release_notes 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_release_notes 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_release_notes. 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_release_notes is provided by the Tickr MCP server (@k-system/tickr-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 →