jira_link_issues · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_link_issues does on Jira MCP Server

AI agents use jira_link_issues 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.

WHY IT NEEDS A POLICY

Why jira_link_issues needs a policy

Creating a link between two Jira issues is a reversible write operation — links can be removed. It modifies the relationship metadata of issues but does not delete or irreversibly alter data, execute code, or involve financial transactions.

From the tool's definition Link two Jira issues

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_link_issues Rate-limited

jira_link_issues 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_link_issues": {
      "limits": [
        {
          "counter": "jira_link_issues_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_link_issues

What does the jira_link_issues tool do? +

Link two Jira issues. 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.

How do I enforce a policy on jira_link_issues? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_link_issues: 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.

What risk level is jira_link_issues? +

jira_link_issues is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_link_issues? +

Yes. Add a rate_limit block to the jira_link_issues 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.

How do I block jira_link_issues completely? +

Set action: deny in the PolicyLayer policy for jira_link_issues. 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.

What MCP server provides jira_link_issues? +

jira_link_issues is provided by the Jira MCP Server MCP server (yogeshhrathod/jiramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.