Link two Jira tickets together with a relationship type. Use jira_get_link_types to discover available link type names. Common types:
AI agents use jira_link_tickets to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
This tool creates a relationship/link between two existing Jira tickets. It modifies data by establishing a connection between tickets, which is reversible (links can be removed). No code execution, deletion, or financial action is involved. Misuse could create incorrect ticket relationships affecting project tracking, hence medium severity.
From the tool's definition Link two Jira tickets together with a relationship type
Attacks that exploit this kind of access
Link two Jira tickets together with a relationship type. Use jira_get_link_types to discover available link type names. Common types:. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_link_tickets: 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 Jira MCP Server. Nothing to install.
jira_link_tickets 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 jira_link_tickets 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 jira_link_tickets. 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.
jira_link_tickets is provided by the Jira MCP Server MCP server (rui-branco/jira-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 →