Get remote issue links (external links) on a Jira issue
AI agents call getJiraIssueRemoteIssueLinks to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data (external links associated with a Jira issue) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk, as it only exposes information already associated with an issue that the requesting user likely has access to.
From the tool's definition Tool retrieves 'remote issue links (external links) on a Jira issue' with no modification, deletion, or execution capability indicated.
Attacks that exploit this kind of access
Get remote issue links (external links) on a Jira issue. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for getJiraIssueRemoteIssueLinks: 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 Atlassian Multi. Nothing to install.
getJiraIssueRemoteIssueLinks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getJiraIssueRemoteIssueLinks 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 getJiraIssueRemoteIssueLinks. 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.
getJiraIssueRemoteIssueLinks is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →