update_jira_ticket · DCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_jira_ticket does on DCI MCP Server

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

WHY IT NEEDS A POLICY

Why update_jira_ticket needs a policy

This tool modifies Jira tickets without deleting them, making it a Write operation. Severity is medium because careless updates to tracked issues could mislead teams or overwrite important information, but changes are reversible. Confidence is lowered slightly (0.75 vs higher) due to the empty description, though the function name is unambiguous.

From the tool's definition Tool name 'update_jira_ticket' indicates modification of existing Jira ticket data. The description is empty, but the name and server context (Jira integration) clearly show this creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_jira_ticket Rate-limited

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

FAQ

Questions about update_jira_ticket

What does the update_jira_ticket tool do? +

update_jira_ticket. It is categorised as a Write tool in the DCI 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 update_jira_ticket? +

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

What risk level is update_jira_ticket? +

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

Can I rate-limit update_jira_ticket? +

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

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

update_jira_ticket is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.