Assign or unassign a Jira issue.
AI agents use jira_assign_issue to create or update resources in Mcp Jira Confluence Corp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Confluence Corp environment.
This tool modifies issue state by changing the assignee field, which is a reversible write operation. It does not delete data (not Destructive), execute code (not Execute), or transfer money (not Financial).
From the tool's definition Tool name 'jira_assign_issue' and description 'Assign or unassign a Jira issue' indicate modification of issue metadata. Server description states 'read/write operations on issues' confirming write capability.
Attacks that exploit this kind of access
Assign or unassign a Jira issue. It is categorised as a Write tool in the Mcp Jira Confluence Corp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Jira Confluence Corp 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 Confluence Corp. 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 Confluence Corp MCP server (mshegolev/mcp-jira-confluence-corp). 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 →