AI agents use add_relation 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 | Yes | Relation type: 'blocks' means source blocks target |
source_number | string | Yes | Source ticket display number, e.g. 'TKR-42' or 'TKR-BUG-0042' |
target_number | string | Yes | Target ticket display number |
Parameters from the server's own tool schema.
This tool creates new relational metadata between tickets (blocks, relates_to, duplicates), which is a reversible modification to the system state. It does not execute code, trigger external operations, or delete data. The blast radius is medium because incorrect relation creation could mislead project dependencies, but it can be undone by removing the relation.
From the tool's definition Create a relation between two tickets (blocks, relates_to, duplicates) — explicitly performs a create action that modifies ticket metadata by establishing new relationships in the project management system.
Attacks that exploit this kind of access
Create a relation between two tickets (blocks, relates_to, duplicates). 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_relation accepts 3 parameters: type, source_number, target_number. Required: type, source_number, target_number. 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_relation: 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_relation 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_relation 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_relation. 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_relation 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 →