Critical Risk →

deleteFilter

Delete a filter in Jira

How to control deleteFilter ↓

AI agents call deleteFilter to permanently remove resources in MCP Atlassian Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes a Jira filter, which is an irreversible action that cannot be undone. Filters may be used by other team members, dashboards, or automation rules, so their deletion could disrupt workflows. This fits the Destructive category (delete operations that cannot be undone).

From the tool's definition Tool name is 'deleteFilter' with description 'Delete a filter in Jira'. The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access deleteFilter gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteFilter:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteFilter"
  ]
}

deleteFilter disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Atlassian Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the deleteFilter tool do? +

Delete a filter in Jira. It is categorised as a Destructive tool in the MCP Atlassian Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deleteFilter? +

Register the MCP Atlassian Server MCP server in PolicyLayer and add a rule for deleteFilter: 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 MCP Atlassian Server. Nothing to install.

What risk level is deleteFilter? +

deleteFilter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteFilter? +

Yes. Add a rate_limit block to the deleteFilter 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.

How do I block deleteFilter completely? +

Set action: deny in the PolicyLayer policy for deleteFilter. 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.

What MCP server provides deleteFilter? +

deleteFilter is provided by the MCP Atlassian Server MCP server (phuc-nt/mcp-atlassian-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Atlassian Server tool call.

Deterministic rules across all 24 MCP Atlassian Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 MCP Atlassian Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.