AI agents use link-tickets to create or update resources in JIRA MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JIRA MCP environment.
Linking tickets creates or modifies ticket relationships (e.g., 'relates to', 'blocks', 'duplicates'), which is a write operation. It is reversible (links can be removed), so it does not qualify as Destructive.
From the tool's definition Tool description states 'Link two jira tickets' — linking establishes a reversible relationship between tickets without deleting, overwriting, or irreversibly destroying data. This is a structural modification to ticket metadata.
Documented attack patterns abuse exactly the kind of access link-tickets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for link-tickets:
{
"version": "1",
"default": "deny",
"tools": {
"link-tickets": {
"limits": [
{
"counter": "link-tickets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link-tickets 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.
Free to start. No card required.
Link two jira tickets. It is categorised as a Write tool in the JIRA MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JIRA MCP server in PolicyLayer and add a rule for link-tickets: 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. Nothing to install.
link-tickets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link-tickets 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 link-tickets. 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.
link-tickets is provided by the JIRA MCP server (mankowskinick/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JIRA MCP, 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.
14 JIRA MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.