jira_create_issue

Create a new Jira issue

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/jira-create-issue.md

WHAT IT DOES

What jira_create_issue does on ScopeGate

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

RISK

Why jira_create_issue is rated Medium

This tool creates new data (a Jira issue) which is reversible through standard Jira deletion/archival mechanisms. It falls under Write category rather than Execute because the action is bounded to data creation rather than arbitrary code execution.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_create_issue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_create_issue, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every jira_create_issue call is checked against it from then on.

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 ScopeGate 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 ScopeGate 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 ScopeGate. 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →