jira_issue_create_tool
AI agents use jira_issue_create_tool to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
Creating a Jira issue is a reversible write operation that adds new data to the system. It modifies state but can be undone by deleting the created issue. This does not execute arbitrary code, delete data irreversibly, or move money, so it falls under Write category.
From the tool's definition Tool name is 'jira_issue_create_tool' which explicitly indicates issue creation functionality. Server description states the tool enables interaction with Jira for 'issue management' and the sibling tools include comment, filter operations confirming a…
Attacks that exploit this kind of access
jira_issue_create_tool. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_issue_create_tool: 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 Server. Nothing to install.
jira_issue_create_tool 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_issue_create_tool 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_issue_create_tool. 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_issue_create_tool is provided by the Jira MCP Server MCP server (troylar/jira-mcp-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 →