delete_sprint

Delete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.

Server Raalarcon Jira raalarcon-jira-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_sprint does on Raalarcon Jira

AI agents call delete_sprint to permanently remove resources in Raalarcon Jira — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_sprint needs a policy

This tool irreversibly deletes data (the sprint itself) and reorganizes related data (moving issues to backlog). Deletion with explicit irreversibility notation is the defining characteristic of the Destructive category. While it doesn't destroy individual issues, it destroys the sprint container and its structure, warranting high severity due to potential workflow disruption in Agile teams.

From the tool's definition Tool description explicitly states: 'Delete a sprint' and 'This action is irreversible.' The tool permanently removes a sprint and relocates its issues, which cannot be undone.

Questions about delete_sprint

What does the delete_sprint tool do? +

Delete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible. It is categorised as a Destructive tool in the Raalarcon Jira 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 delete_sprint? +

Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for 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 Raalarcon Jira. Nothing to install.

What risk level is delete_sprint? +

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

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

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

delete_sprint is provided by the Raalarcon Jira MCP server (raalarcon-jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.