Delete a worklog from a Jira ticket
AI agents call delete_worklog to permanently remove resources in Jira — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes worklog entries from Jira tickets. Worklogs are time-tracking records that may be used for billing, reporting, or compliance purposes. Deletion of these records cannot be undone and destroys audit trails and historical data.
From the tool's definition Tool name is 'delete_worklog' and description states 'Delete a worklog from a Jira ticket'. The verb 'delete' combined with the action of removing worklog data indicates irreversible data removal.
Attacks that exploit this kind of access
Delete a worklog from a Jira ticket. It is categorised as a Destructive tool in the Jira MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira MCP server in PolicyLayer and add a rule for delete_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.
delete_worklog is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →