create_jira_issue · Enterprise AI Bridge (MCP) MCP

WHAT IT DOES

What create_jira_issue does on Enterprise AI Bridge (MCP)

AI agents use create_jira_issue to create or update resources in Enterprise AI Bridge (MCP) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enterprise AI Bridge (MCP) environment.

WHY IT NEEDS A POLICY

Why create_jira_issue needs a policy

The tool creates new Jira issues, which is a Write operation (creates data reversibly). Severity is medium because uncontrolled creation could spam the issue tracker, waste engineering time triaging spurious tasks, or disrupt workflows, but the effects are reversible and don't directly cause financial loss or data destruction. Confidence is high (0.95) given the explicit 'create' verb and clear description.

From the tool's definition Tool name 'create_jira_issue' and description 'Creates a new Jira task' indicate data creation. This is a reversible write operation—tasks can be edited or deleted after creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_jira_issue Rate-limited

create_jira_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_jira_issue": {
      "limits": [
        {
          "counter": "create_jira_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 Enterprise AI Bridge (MCP), so you can run agents against it safely.

FAQ

Questions about create_jira_issue

What does the create_jira_issue tool do? +

Creates a new Jira task. It is categorised as a Write tool in the Enterprise AI Bridge (MCP) 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_jira_issue? +

Register the Enterprise AI Bridge (MCP) MCP server in PolicyLayer and add a rule for create_jira_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 Enterprise AI Bridge (MCP). Nothing to install.

What risk level is create_jira_issue? +

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

Can I rate-limit create_jira_issue? +

Yes. Add a rate_limit block to the create_jira_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_jira_issue completely? +

Set action: deny in the PolicyLayer policy for create_jira_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_jira_issue? +

create_jira_issue is provided by the Enterprise AI Bridge (MCP) MCP server (olegvasilievcs/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.