AI agents use update_release to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New release name |
notes | string | — | Release notes (markdown) |
status | string | — | New status: draft, published, archived |
project | string | Yes | Project slug |
release_id | string | Yes | UUID of the release to update |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly without deleting or executing external operations. Updating release attributes (name, notes, status) are write operations that can be undone or changed. In a project management context, releasing software can have downstream consequences, but the tool itself only modifies release metadata, not code or deployment infrastructure, warranting medium severity rather than high.
From the tool's definition Tool name is 'update_release' and description states it can 'Update a release (name, notes, status)' — modifying release metadata including name, notes, and status.
Attacks that exploit this kind of access
Update a release (name, notes, status). It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_release accepts 5 parameters: name, notes, status, 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 update_release: 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.
update_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_release 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 update_release. 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.
update_release 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 →