update_worklog · Jira MCP: Risk & Policy

WHAT IT DOES

What update_worklog does on Jira

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

WHY IT NEEDS A POLICY

Why update_worklog needs a policy

This tool modifies existing worklog records in Jira, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions. The medium severity reflects that misuse could corrupt time tracking data affecting project metrics and reporting, but the impact is limited to a single worklog entry and remains correctable.

From the tool's definition Tool name 'update_worklog' and description 'Update an existing worklog on a Jira ticket' indicate modification of existing data. Worklog entries track time spent on tasks and are reversible changes (can be edited or deleted later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_worklog Rate-limited

update_worklog 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_worklog": {
      "limits": [
        {
          "counter": "update_worklog_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, so you can run agents against it safely.

FAQ

Questions about update_worklog

What does the update_worklog tool do? +

Update an existing worklog on a Jira ticket. It is categorised as a Write tool in the Jira 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_worklog? +

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

What risk level is update_worklog? +

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

Can I rate-limit update_worklog? +

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

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

update_worklog is provided by the Jira MCP server (taraskhust/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.