create_data_quality_ticket · Jira MCP Server MCP

WHAT IT DOES

What create_data_quality_ticket does on Jira MCP Server

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

WHY IT NEEDS A POLICY

Why create_data_quality_ticket needs a policy

This tool creates data within Jira (a ticket), which is a reversible modification operation (tickets can be edited or deleted later). It does not execute arbitrary code, delete data, move money, or retrieve information without side effects. The severity is medium because malicious ticket creation could spam the system, but the impact is limited to Jira records and does not affect production systems directly.

From the tool's definition Tool name contains 'create' and description states 'Create a standardized data quality ticket' — this creates a new record (ticket) in Jira.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_data_quality_ticket Rate-limited

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

FAQ

Questions about create_data_quality_ticket

What does the create_data_quality_ticket tool do? +

Create a standardized data quality ticket for reporting system failures. This is the standard format for reporting data issues identified through database queries (e.g., a store with 0 people). It is categorised as a Write tool in the Jira 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_data_quality_ticket? +

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

What risk level is create_data_quality_ticket? +

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

Can I rate-limit create_data_quality_ticket? +

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

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

create_data_quality_ticket is provided by the Jira MCP Server MCP server (raulubillos/mcpserverjira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.