create_jira_ticket · Error Tracker MCP Server MCP

WHAT IT DOES

What create_jira_ticket does on Error Tracker MCP Server

AI agents use create_jira_ticket to create or update resources in Error Tracker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Error Tracker MCP Server environment.

WHY IT NEEDS A POLICY

Why create_jira_ticket needs a policy

This tool creates new records (JIRA tickets) in an external issue tracking system, which is a reversible write operation. While it can assign issues and potentially trigger notifications/workflows, the core action is creating/modifying data. It does not execute arbitrary code, delete data, or move money.

From the tool's definition Tool description states 'Create a JIRA ticket' which is a create operation that modifies data (adds a new ticket to the JIRA system). The tool generates and persists structured data in an external system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_jira_ticket Rate-limited

create_jira_ticket 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_ticket": {
      "limits": [
        {
          "counter": "create_jira_ticket_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 Error Tracker MCP Server, so you can run agents against it safely.

FAQ

Questions about create_jira_ticket

What does the create_jira_ticket tool do? +

Create a JIRA ticket with AI-generated error analysis and investigation results from investigate_error tool. It is categorised as a Write tool in the Error Tracker 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_jira_ticket? +

Register the Error Tracker MCP Server MCP server in PolicyLayer and add a rule for create_jira_ticket: 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 Error Tracker MCP Server. Nothing to install.

What risk level is create_jira_ticket? +

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

Can I rate-limit create_jira_ticket? +

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

Set action: deny in the PolicyLayer policy for create_jira_ticket. 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_ticket? +

create_jira_ticket is provided by the Error Tracker MCP Server MCP server (wyccome/mcp-error-tracing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.