create_issue · Raalarcon Jira MCP: Risk & Policy

WHAT IT DOES

What create_issue does on Raalarcon Jira

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

WHY IT NEEDS A POLICY

Why create_issue needs a policy

This tool creates new issues in Jira, which is a write operation that modifies the project state by adding data. It is reversible (issues can be deleted), so it does not qualify as Destructive. The blast radius is medium because an agent could create numerous spam issues or issues with malicious content, but damage can be undone through deletion. It does not execute code, move money, or irreversibly destroy data.

From the tool's definition Tool description states 'Create a new Jira issue' and 'Returns the created issue key, ID, and URL', indicating creation of new data in Jira. The tool is reversible via delete_issue (present as sibling tool).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue Rate-limited

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": {
    "create_issue": {
      "limits": [
        {
          "counter": "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 Raalarcon Jira, so you can run agents against it safely.

FAQ

Questions about create_issue

What does the create_issue tool do? +

Create a new Jira issue (Bug, Story, Task, Epic, etc.) or subtask. Returns the created issue key, ID, and URL. Use get_issue_types to find valid issueType values for the project. To create a subtask, specify the parent issue key. It is categorised as a Write tool in the Raalarcon Jira 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? +

Register the Raalarcon 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 Raalarcon Jira. Nothing to install.

What risk level is create_issue? +

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

Can I rate-limit create_issue? +

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.

How do I block create_issue completely? +

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.

What MCP server provides create_issue? +

create_issue is provided by the Raalarcon Jira MCP server (raalarcon-jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.