Manage Jira issue links: add, remove, list relationships between two issues. Use get_link_types first to discover the available link names in the target Jira instance — they vary per project config.
AI agents use jira_links 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.
The tool creates and removes links between issues. 'Remove' could be considered destructive, but issue links are metadata relationships that can be re-added, making the operation reversible. 'Add' and 'list' are Write/Read operations. The most severe applicable category for managing (add/remove) reversible relationships is Write.
From the tool's definition Manage Jira issue links: add, remove, list relationships between two issues
Documented attack patterns abuse exactly the kind of access jira_links gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_links:
{
"version": "1",
"default": "deny",
"tools": {
"jira_links": {
"limits": [
{
"counter": "jira_links_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_links stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage Jira issue links: add, remove, list relationships between two issues. Use get_link_types first to discover the available link names in the target Jira instance — they vary per project config. 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_links: 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_links 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_links 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_links. 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_links is provided by the Jira MCP Server MCP server (pdogra1299/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.