Get all available issue link types. Returns link type names, inward/outward descriptions.
AI agents call jira_get_issue_link_types to retrieve information from Atlassian 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 metadata about issue link types in Jira—specifically their names and directional descriptions. It performs no writes, deletions, code execution, or financial operations. The data retrieved is configuration metadata with no blast radius if misused by an agent, as it cannot modify system state or trigger external actions.
From the tool's definition Tool description states 'Get all available issue link types' and 'Returns link type names, inward/outward descriptions.' The verb 'Get' and 'Returns' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access jira_get_issue_link_types gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_get_issue_link_types:
{
"version": "1",
"default": "deny",
"tools": {
"jira_get_issue_link_types": {}
}
}jira_get_issue_link_types is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all available issue link types. Returns link type names, inward/outward descriptions. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP server in PolicyLayer and add a rule for jira_get_issue_link_types: 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. Nothing to install.
jira_get_issue_link_types 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 jira_get_issue_link_types 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_get_issue_link_types. 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_get_issue_link_types is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, 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.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.