Assign a JIRA issue to a user or unassign.
AI agents use jira_assign_issue to create or update resources in MCP JIRA Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP JIRA Server environment.
This tool creates or modifies issue metadata (assignee field) reversibly. An AI agent could reassign issues incorrectly, causing workflow disruptions or redirecting work inappropriately, but the action is not destructive and can be undone by reassigning again. It does not execute code, delete data, or move money.
From the tool's definition The tool name and description indicate it performs assignment operations on JIRA issues: 'Assign a JIRA issue to a user or unassign.' This is a reversible modification operation that changes issue state without deleting data.
Attacks that exploit this kind of access
Assign a JIRA issue to a user or unassign. It is categorised as a Write tool in the MCP JIRA Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP JIRA Server MCP server in PolicyLayer and add a rule for jira_assign_issue: 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 JIRA Server. Nothing to install.
jira_assign_issue 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_assign_issue 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_assign_issue. 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_assign_issue is provided by the MCP JIRA Server MCP server (tarangbhavsar/mcp-jira-server). 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 →