AI agents use add_epic_dependency 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 |
|---|---|---|---|
type | string | — | Dependency type: finish-to-start (default), start-to-start, finish-to-finish, start-to-finish |
project | string | Yes | Project slug |
successor_epic_id | string | Yes | UUID of the successor epic (depends on predecessor) |
predecessor_epic_id | string | Yes | UUID of the predecessor epic (must finish first) |
Parameters from the server's own tool schema.
This tool creates a new relationship in the project management model, which is a reversible modification (the dependency can presumably be removed). It does not execute arbitrary code, delete data, move money, or read-only query.
From the tool's definition add_epic_dependency adds a dependency relationship between two epics, creating or modifying a directed relationship in the project management system. The description explicitly states 'Add a dependency...
Attacks that exploit this kind of access
Add a dependency between two epics (predecessor blocks successor). 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.
add_epic_dependency accepts 4 parameters: type, project, successor_epic_id, predecessor_epic_id. Required: project, successor_epic_id, predecessor_epic_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 add_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.
add_epic_dependency 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 add_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 add_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.
add_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 →