AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Epic name |
color | string | — | Epic color hex code (e.g. #6366f1) |
project | string | Yes | Project slug |
start_date | string | — | Start date (YYYY-MM-DD) |
description | string | — | Epic description |
external_id | string | — | External identifier for linking to other systems |
target_date | string | — | Target date (YYYY-MM-DD) |
Parameters from the server's own tool schema.
This tool creates new project management data (an epic) which is reversible through deletion or modification. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external side effects beyond the scope of the project management system.
From the tool's definition Tool name 'create_epic' and description 'Create a new epic in a project' indicate data creation that modifies project state by adding a new epic.
Attacks that exploit this kind of access
Create a new epic 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_epic accepts 7 parameters: name, color, project, start_date, description, external_id, target_date. Required: name, 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 create_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.
create_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 create_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 create_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.
create_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 →