assign_jira_issue · Enterprise AI Bridge (MCP) MCP

WHAT IT DOES

What assign_jira_issue does on Enterprise AI Bridge (MCP)

AI agents use assign_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 assign_jira_issue needs a policy

Assigning an issue to a user modifies project data reversibly. The assignee can be changed again, making this a Write operation rather than Destructive. Severity is medium because misuse could reassign critical work inappropriately, disrupting team workflow, but the action is not financial and is easily reversible.

From the tool's definition Tool name 'assign_jira_issue' and description 'Assign a Jira issue by its key... and account id' indicate modifying issue metadata (assignment) without deletion or irreversible change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_jira_issue Rate-limited

assign_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": {
    "assign_jira_issue": {
      "limits": [
        {
          "counter": "assign_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 assign_jira_issue

What does the assign_jira_issue tool do? +

Assign a Jira issue by its key (e.g., 'KAN-7') and account id. 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 assign_jira_issue? +

Register the Enterprise AI Bridge (MCP) MCP server in PolicyLayer and add a rule for assign_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 assign_jira_issue? +

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

Can I rate-limit assign_jira_issue? +

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

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

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