jira_create_remote_issue_link · Jirax MCP: Risk & Policy

WHAT IT DOES

What jira_create_remote_issue_link does on Jiraxmcp

AI agents use jira_create_remote_issue_link to create or update resources in Jiraxmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jiraxmcp environment.

WHY IT NEEDS A POLICY

Why jira_create_remote_issue_link needs a policy

Creating a remote issue link modifies issue data by adding a reference/attachment, but does not delete data or trigger external code execution. This qualifies as a Write operation. Severity is medium because while the change is reversible, modifying issue metadata could affect issue tracking, documentation, or integrations if done incorrectly or maliciously.

From the tool's definition 'Attach a remote URL to a Jira issue' indicates the tool creates or modifies metadata on an existing issue by adding a link. This is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_create_remote_issue_link Rate-limited

jira_create_remote_issue_link 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_create_remote_issue_link": {
      "limits": [
        {
          "counter": "jira_create_remote_issue_link_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 Jiraxmcp, so you can run agents against it safely.

FAQ

Questions about jira_create_remote_issue_link

What does the jira_create_remote_issue_link tool do? +

Attach a remote URL to a Jira issue. It is categorised as a Write tool in the Jiraxmcp 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_create_remote_issue_link? +

Register the Jirax MCP server in PolicyLayer and add a rule for jira_create_remote_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 Jiraxmcp. Nothing to install.

What risk level is jira_create_remote_issue_link? +

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

Can I rate-limit jira_create_remote_issue_link? +

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

How do I block jira_create_remote_issue_link completely? +

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

What MCP server provides jira_create_remote_issue_link? +

jira_create_remote_issue_link is provided by the Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.