This record as markdown: /tools/1broseidon-mcp-jira-server/create-issue.md
What create_issue does on Mcp Jira
AI agents use create_issue to create or update resources in Mcp Jira, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira environment.
Why create_issue is rated Medium
Creating a Jira issue is a reversible write operation that adds data to the system. It does not execute arbitrary code, destroy data, move funds, or have irreversible side effects. The impact is limited to creating a trackable artifact in a project management system, which is low severity for an AI agent misuse context.
From the tool's definition Tool name 'create_issue' and description 'Create a new Jira issue' indicate creation of new data in the Jira system.
Attacks that exploit this kind of access
The rule that runs create_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Jira, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_issue, this is the rule to start with:
create_issue 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Jira, apply this rule, and every create_issue call is checked against it from then on.
Questions about create_issue
Create a new Jira issue. It is categorised as a Write tool in the Mcp Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Jira MCP server in PolicyLayer and add a rule for create_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. Nothing to install.
create_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 create_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 create_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.
create_issue is provided by the Mcp Jira MCP server (1broseidon/mcp-jira-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Jira, and thousands of servers like it.
This server
Across the catalogue