Get all available issue link types.
AI agents call get_link_types to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about issue link types in Jira, returning information about available relationships between issues. It produces no side effects, creates no data, executes no code, and cannot delete or modify anything. The blast radius of misuse is minimal—an attacker could only learn what link types exist in the system, which is generally low-sensitivity configuration information.
From the tool's definition Tool name 'get_link_types' and description 'Get all available issue link types' indicate a retrieval operation with no modification of data. The verb 'Get' and the read-only nature of querying available link types confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get all available issue link types. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for get_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 MCP Atlassian. Nothing to install.
get_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 get_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 get_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.
get_link_types is provided by the MCP Atlassian MCP server (omkar9854/mcp-atlassian-onpremdc). 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 →