AI agents use jira_create_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.
Creating issue links modifies Jira's data model by establishing relationships between issues (e.g., dependency, relates-to, blocks), but this is reversible—links can be deleted. This is less severe than Destructive operations (delete_issue on the same server) and does not execute arbitrary code or move financial resources.
From the tool's definition Tool creates a link between two Jira issues. The word 'create' indicates a reversible data modification operation.
Attacks that exploit this kind of access
Create a link between two Jira issues. 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.
Register the Jirax MCP server in PolicyLayer and add a rule for jira_create_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.
jira_create_issue_link 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 jira_create_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.
Set action: deny in the PolicyLayer policy for jira_create_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.
jira_create_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.
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 →