Remove a relation from a ticket by relation ID
AI agents call remove_relation 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 |
|---|---|---|---|
relation_id | string | Yes | Relation UUID to remove (from get_ticket relations list) |
source_number | string | Yes | Ticket display number that owns the relation, e.g. 'TKR-42' |
Parameters from the server's own tool schema.
Removing a relation is an irreversible deletion of a specific relationship between tickets. Unlike updating or modifying data, deleting a relation by ID cannot be undone without re-creating it, making this a Destructive action. Severity is medium since only a ticket relationship is lost, not core data.
From the tool's definition "Remove a relation from a ticket by relation ID"
Attacks that exploit this kind of access
Remove a relation from a ticket by relation ID. 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_relation accepts 2 parameters: relation_id, source_number. Required: relation_id, source_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 remove_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.
remove_relation 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_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 remove_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.
remove_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 →