Remove a dependency between two epics
AI agents call remove_epic_dependency 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 either epic in the dependency |
project | string | Yes | Project slug |
dependency_id | string | Yes | UUID of the dependency to remove |
Parameters from the server's own tool schema.
Removing a dependency between epics is a destructive action that deletes an existing relationship. While it doesn't delete the epics themselves, dependency relationships are structural project management data that, once removed, may not be easily reconstructed, especially if the original configuration is not documented.
From the tool's definition 'Remove a dependency between two epics' — the word 'remove' indicates an irreversible deletion of a relationship between epics
Attacks that exploit this kind of access
Remove a dependency between two epics. 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.
remove_epic_dependency accepts 3 parameters: epic_id, project, dependency_id. Required: epic_id, project, dependency_id. 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 remove_epic_dependency: 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.
remove_epic_dependency 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 remove_epic_dependency 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 remove_epic_dependency. 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.
remove_epic_dependency 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 →