jira_add_worklog · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_add_worklog does on Jira MCP Server

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

This tool creates new worklog entries on Jira tickets, which is a write operation that modifies project data. While worklogs can theoretically be removed or corrected, the primary function is to create and persist new time-tracking records. This is more severe than a Read operation but less severe than Destructive (which would be irreversible deletion) or Execute (which would run arbitrary code).

From the tool's definition Tool description states 'Log time/work on a Jira ticket', indicating creation/modification of worklog data. The action is reversible (worklogs can be edited or deleted by administrators), and it modifies Jira ticket records by adding time tracking information.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_add_worklog Rate-limited

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

FAQ

Questions about jira_add_worklog

What does the jira_add_worklog tool do? +

Log time/work on a Jira ticket. Use Jira time format for timeSpent (e.g.,. 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 jira_add_worklog? +

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

What risk level is jira_add_worklog? +

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

Can I rate-limit jira_add_worklog? +

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

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

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