Creates a link between two Jira issues. Supports common link types like "blocks", "relates", "duplicates", and "clones". Use this to establish relationships between issues.
AI agents use jira_create_issue_link to create or update resources in Mcp Jira Stdio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Stdio environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
toIssue | string | Yes | Target issue key |
linkType | string | Yes | Link type: "blocks", "is blocked by", "relates", "duplicates", "clones", or custom link type name |
fromIssue | string | Yes | Source issue key |
Parameters from the server's own tool schema.
The tool creates new relationships/metadata between existing issues (link creation), which is a reversible modification operation. This falls under Write category rather than Execute because it does not run arbitrary code or trigger external operations—it merely establishes a predefined relationship type between issues.
From the tool's definition Creates a link between two Jira issues. Supports common link types like 'blocks', 'relates', 'duplicates', and 'clones'. Use this to establish relationships between issues.
Attacks that exploit this kind of access
Creates a link between two Jira issues. Supports common link types like "blocks", "relates", "duplicates", and "clones". Use this to establish relationships between issues. It is categorised as a Write tool in the Mcp Jira Stdio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
jira_create_issue_link accepts 3 parameters: toIssue, linkType, fromIssue. Required: toIssue, linkType, fromIssue. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_create_issue_link: 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 Mcp Jira Stdio. Nothing to install.
jira_create_issue_link 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_create_issue_link 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_create_issue_link. 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_create_issue_link is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →