AI agents use assign_epic 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 |
|---|---|---|---|
number | string | Yes | Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed) |
epic_id | string | Yes | UUID of the epic |
project | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool modifies ticket metadata by establishing a relationship between a ticket and an epic. It is a Write operation because it creates/modifies data reversibly (the assignment can be undone). The severity is medium because incorrect assignments could disrupt project organization and workflow, but the blast radius is limited to ticket categorization without affecting data integrity or external systems.
From the tool's definition Tool name 'assign_epic' and description 'Assign a ticket to an epic' indicate a modification operation that links/associates a ticket with an epic, which is a reversible write action.
Attacks that exploit this kind of access
Assign a ticket to an epic. 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.
assign_epic accepts 3 parameters: number, epic_id, project. Required: number, epic_id, project. 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 assign_epic: 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.
assign_epic 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 assign_epic 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 assign_epic. 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.
assign_epic 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 →