Deletes a comment from a Jira issue.
AI agents call jira_delete_comment to permanently remove resources in Atlassian — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of comments is an irreversible action that cannot be undone. This falls squarely into the Destructive category. While the blast radius is limited to a single comment rather than entire issues or datasets, the action is permanent and could impact audit trails, team communication, or compliance records.
From the tool's definition Tool name is 'jira_delete_comment' and description states 'Deletes a comment from a Jira issue' — the verb 'Deletes' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a comment from a Jira issue. It is categorised as a Destructive tool in the Atlassian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Atlassian MCP server in PolicyLayer and add a rule for jira_delete_comment: 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 Atlassian. Nothing to install.
jira_delete_comment 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 jira_delete_comment 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 jira_delete_comment. 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.
jira_delete_comment is provided by the Atlassian MCP server (tingyiy/atlassian-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 →