create_issue_tool · JIRA MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_issue_tool does on JIRA MCP Server

AI agents use create_issue_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.

WHY IT NEEDS A POLICY

Why create_issue_tool needs a policy

Creating JIRA issues is a Write operation—it generates new data that can be modified or deleted later. Severity is high because an AI agent could maliciously or accidentally create many issues, spam workflows, or create fake tasks that disrupt project management. Confidence is 0.85 rather than higher because the description is missing; however, the name and sibling context provide strong signal.

From the tool's definition Tool name is 'create_issue_tool' which explicitly creates new data in JIRA. Description is empty, but the name and context (sibling tools like update_issue_tool, clone_issue_tool) confirm this creates reversible records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue_tool Rate-limited

create_issue_tool 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": {
    "create_issue_tool": {
      "limits": [
        {
          "counter": "create_issue_tool_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_issue_tool

What does the create_issue_tool tool do? +

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

How do I enforce a policy on create_issue_tool? +

Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for create_issue_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.

What risk level is create_issue_tool? +

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

Can I rate-limit create_issue_tool? +

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

How do I block create_issue_tool completely? +

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

What MCP server provides create_issue_tool? +

create_issue_tool is provided by the JIRA MCP Server MCP server (klauseduard/vibe-coded-jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.