[Stable] Permanently delete a Redmine issue and all its journals and attachments. This action cannot be undone.
AI agents call redmine_delete_issue to permanently remove resources in Redmine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (issue, journals, attachments) with no undo capability. This is the defining characteristic of the Destructive category. The high severity reflects the permanent loss of potentially important project tracking data and associated information.
From the tool's definition Permanently delete a Redmine issue and all its journals and attachments. This action cannot be undone.
Attacks that exploit this kind of access
[Stable] Permanently delete a Redmine issue and all its journals and attachments. This action cannot be undone. It is categorised as a Destructive tool in the Redmine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redmine MCP server in PolicyLayer and add a rule for redmine_delete_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 Redmine. Nothing to install.
redmine_delete_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 redmine_delete_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 redmine_delete_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.
redmine_delete_issue is provided by the Redmine MCP server (jesusr00/mcp-server-redmine). 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 →