jira_delete_sprint

THE RISK

Critical Risk

Why jira_delete_sprint needs a policy

This tool irreversibly deletes sprint data, which is a permanent destructive action. Although the tool has built-in constraints (only future sprints), the core function is deletion/destruction of data structures. This falls squarely into the Destructive category, which is more severe than Write.

From the tool's definition Tool name explicitly states 'delete_sprint' and description confirms it 'Delete a sprint' - an irreversible operation that removes sprint data and cannot be undone.

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

POLICY

How to control jira_delete_sprint

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "jira_delete_sprint"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Atlassian tools

Destructive confluence_delete_page Delete a page. By default, moves to trash. Use purge option for permanent deletion. Destructive jira_delete_board Delete a board. Warning: This is permanent and cannot be undone. All board configuration w Destructive jira_delete_issue Delete a Jira issue. This action cannot be undone unless the issue is in the trash. Destructive jira_remove_issue_link Remove/delete a link between two issues. Requires the link ID. Write jira_link_to_epic Link multiple issues to an epic. Creates Epic-Story links between issues and epic. Write jira_rank_backlog_issues Rank/reorder issues in the backlog. Used to adjust issue priority order before sprint plan Write confluence_add_comment Add a footer comment to a page. Can be a top-level comment or a reply to another comment. Write confluence_add_label Add one or more labels to a page. Labels help organize and categorize content.

All 51 Atlassian tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Atlassian → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about jira_delete_sprint

What does the jira_delete_sprint tool do? +

Delete a sprint. Note: Can only delete sprints that have not been started (future state). Cannot delete active or closed sprints. 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.

How do I enforce a policy on jira_delete_sprint? +

Register the Atlassian MCP server in PolicyLayer and add a rule for jira_delete_sprint: 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.

What risk level is jira_delete_sprint? +

jira_delete_sprint 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 jira_delete_sprint? +

Yes. Add a rate_limit block to the jira_delete_sprint 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 jira_delete_sprint completely? +

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

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

Enforce policy on every Atlassian tool call.

Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →