jira_comment_delete_tool
AI agents call jira_comment_delete_tool to permanently remove resources in Jira MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' suffix strongly implies irreversible deletion of a Jira comment. Deletion of comments cannot be undone, placing this in the Destructive category. Severity is high because an AI agent could delete important comments or audit trail information. Confidence is slightly reduced due to the empty description.
From the tool's definition Tool name 'jira_comment_delete_tool' contains 'delete', indicating irreversible removal of a comment. Description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
jira_comment_delete_tool. It is categorised as a Destructive tool in the Jira MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_comment_delete_tool: 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.
jira_comment_delete_tool 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_comment_delete_tool 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_comment_delete_tool. 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_comment_delete_tool is provided by the Jira MCP Server MCP server (troylar/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 →