jira_create_issue · Jira & Confluence MCP Server MCP

WHAT IT DOES

What jira_create_issue does on Jira & Confluence MCP Server

AI agents use jira_create_issue to create or update resources in Jira & Confluence MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira & Confluence MCP Server environment.

WHY IT NEEDS A POLICY

Why jira_create_issue needs a policy

Creating a Jira issue is a reversible write operation that modifies the Jira system state by adding a new record. It does not execute arbitrary code, delete data irreversibly, or move money. However, it has medium severity because unconstrained issue creation could spam the system, disrupt workflows, or create misleading project records that administrative cleanup would be required to resolve.

From the tool's definition Tool name 'jira_create_issue' and description 'Create a new Jira issue' indicate creation of new data in Jira.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_create_issue Rate-limited

jira_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_create_issue": {
      "limits": [
        {
          "counter": "jira_create_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira & Confluence MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_create_issue

What does the jira_create_issue tool do? +

Create a new Jira issue. It is categorised as a Write tool in the Jira & Confluence MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jira_create_issue? +

Register the Jira & Confluence MCP Server MCP server in PolicyLayer and add a rule for jira_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 Jira & Confluence MCP Server. Nothing to install.

What risk level is jira_create_issue? +

jira_create_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_create_issue? +

Yes. Add a rate_limit block to the jira_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.

How do I block jira_create_issue completely? +

Set action: deny in the PolicyLayer policy for jira_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.

What MCP server provides jira_create_issue? +

jira_create_issue is provided by the Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.