Deletes a Jira issue by its key (e.g., 'KAN-7').
AI agents call delete_jira_issue to permanently remove resources in Enterprise AI Bridge (MCP) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of Jira issues is an irreversible action that cannot be undone through normal means. This falls squarely into the Destructive category. The severity is high because accidental or malicious deletion of project issues could disrupt team workflows, lose important tracking information, and potentially impact project management and compliance.
From the tool's definition The tool name is 'delete_jira_issue' and the description states it 'Deletes a Jira issue by its key'. The verb 'deletes' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a Jira issue by its key (e.g., 'KAN-7'). It is categorised as a Destructive tool in the Enterprise AI Bridge (MCP) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enterprise AI Bridge (MCP) MCP server in PolicyLayer and add a rule for delete_jira_issue: 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 Enterprise AI Bridge (MCP). Nothing to install.
delete_jira_issue 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_jira_issue 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_jira_issue. 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_jira_issue is provided by the Enterprise AI Bridge (MCP) MCP server (olegvasilievcs/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 →