Delete an issue category.
AI agents call delete_issue_category 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.
This tool permanently removes an issue category from a Redmine instance, which is an irreversible operation. While not critical in terms of immediate financial or system-wide impact, deleting a category could affect issue organization and tracking for all associated issues in the system. The effect cannot be undone through normal operations, making it Destructive rather than Write.
From the tool's definition Tool name explicitly states 'delete_issue_category' and description confirms 'Delete an issue category.' The verb 'delete' combined with 'category' indicates irreversible removal of a data structure that may be associated with multiple issues.
Attacks that exploit this kind of access
Delete an issue category. 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 delete_issue_category: 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.
delete_issue_category 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 delete_issue_category 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 delete_issue_category. 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.
delete_issue_category is provided by the Redmine MCP server (yenpu/redmine-mcp). 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 →