Delete an epic from a project
AI agents call delete_epic to permanently remove resources in Tickr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
epic_id | string | Yes | UUID of the epic to delete |
project | string | Yes | Project slug |
Parameters from the server's own tool schema.
Deleting an epic from a project management system removes the epic and likely its associated metadata irreversibly. This cannot be undone through normal tool operations, making it a destructive action. The blast radius is high because accidental deletion of an epic could lose significant project organization, linked tasks, and historical context.
From the tool's definition Tool name is 'delete_epic' and description states 'Delete an epic from a project' — delete operations irreversibly remove data.
Attacks that exploit this kind of access
Delete an epic from a project. It is categorised as a Destructive tool in the Tickr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_epic accepts 2 parameters: epic_id, project. 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 delete_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.
delete_epic is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →