AI agents use update_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 | — | New epic name |
color | string | — | New hex color code, e.g. '#6366f1' |
epic_id | string | Yes | UUID of the epic to update |
project | string | Yes | Project slug |
startDate | string | — | New start date (YYYY-MM-DD) |
targetDate | string | — | New target date (YYYY-MM-DD) |
description | string | — | New epic description |
external_id | string | — | External identifier |
Parameters from the server's own tool schema.
This tool modifies project management data (epics) in a reversible manner. Updates are typical Write operations that change state but allow correction or rollback. The blast radius is medium because misconfigured epic updates could disrupt project planning and tracking, but they don't delete data, execute arbitrary code, or cause financial impact.
From the tool's definition Tool name 'update_epic' and description 'Update an epic in a project' indicate modification of existing epic data.
Attacks that exploit this kind of access
Update an 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.
update_epic accepts 8 parameters: name, color, epic_id, project, startDate, targetDate, description, external_id. Required: 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 update_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.
update_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 update_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 update_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.
update_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 →