Delete a filter.
AI agents call jira_filter_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.
This tool permanently removes a Jira filter, which cannot be undone. Even though the blast radius is limited to a single filter (not data loss), deletion is an irreversible destructive action. It ranks higher than Write (which are reversible modifications) and falls under Destructive category.
From the tool's definition Tool name is 'jira_filter_delete_tool' with description 'Delete a filter.' The verb 'delete' and explicit action of removing a filter is irreversible.
Attacks that exploit this kind of access
Delete a filter. 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_filter_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_filter_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_filter_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_filter_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_filter_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 →