jira_create_issue · GitHub-Jira MCP Server MCP

WHAT IT DOES

What jira_create_issue does on GitHub-Jira MCP Server

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

WHY IT NEEDS A POLICY

Why jira_create_issue needs a policy

Creating a Jira issue is a reversible write operation—it generates new data in the Jira system without destructive or financial implications. An AI agent misusing this tool could spam issues or create misleading tickets, impacting team workflows and potentially causing operational confusion, warranting medium severity.

From the tool's definition Tool name is 'jira_create_issue' and sibling context shows this server manages 'create issues' in Jira project workflows. The description is empty, but the name and server context clearly indicate issue creation.

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 GitHub-Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_create_issue

What does the jira_create_issue tool do? +

jira_create_issue. It is categorised as a Write tool in the GitHub-Jira 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 GitHub-Jira 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 GitHub-Jira 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 GitHub-Jira MCP Server MCP server (kronoswastaken/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.