AI agents use create_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 | — | Human-readable release name |
git_tag | string | — | Git tag name, e.g. 'v1.6.0' |
project | string | Yes | Project slug, e.g. 'tickr' |
version | string | Yes | Semantic version, e.g. '1.6.0' |
cycle_id | string | — | UUID of linked cycle (sprint) |
Parameters from the server's own tool schema.
Creating a release is a reversible write operation that modifies project state by adding a new release record. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because a malicious or mistaken release creation could disrupt release workflows and require manual cleanup, but the action itself is not destructive and can be undone by deleting the release.
From the tool's definition Tool name is 'create_release' and description states 'Create a new release in a project' — this creates a new structured data entity (a release) within the project management system.
Attacks that exploit this kind of access
Create a new release in a project. 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.
create_release accepts 5 parameters: name, git_tag, project, version, cycle_id. Required: project, version. 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 create_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.
create_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 create_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 create_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.
create_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 →