AI agents use add_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.
This tool creates or appends worklog records to tickets, which is a reversible modification of data. It does not delete, execute code, move financial resources, or trigger external operations. It falls squarely into Write category as it records and potentially modifies time tracking data on a ticket.
From the tool's definition add_worklog adds time tracking information to a Jira ticket. This creates new data (worklog entry) and modifies the ticket's time tracking state. The tool description explicitly states it adds a worklog, which is a create/record action without deletion.
Attacks that exploit this kind of access
Add worklog (time spent) to 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.
Register the Jira MCP server in PolicyLayer and add a rule for 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. Nothing to install.
add_worklog is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
add_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.
add_worklog is one line of Jira's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →